Loading XML into Java^(tm) normally means that...

• The amount of code to load and process the XML is bigger than the XML or
• The code to process the XML needs regenerating each time the XML changes or
• You need two passes to get the XML in the right place - your objects

What's required is a set of classes that are simple and easy to use, can load the XML without the need for code generation and compilation, and can put the XML where it should be.

It's exactly that. For quick and easy XML processing, it will load it into a set of objects which can be handled using standard iterators.

When more power is required a mapping can be used. Based on this mapping the XML elements, attributes and data will be assigned to objects, methods and properties of Java^(tm) classes. This removes the need for multiple passes of the XML, and associated objects, or for the generation and compilation of code when the XML format changes.

Currently Metalised XML is only available from the CVS on SourceForge. For details on this follow the CVS link from the Metalised XML project page. From here you can also post feature requests and log any errors.

Those of you using Eclipse can access the repository via the CVS perspective. Use the settings as described on the project page.

The API documentation is available here. A developers guide, including descriptions of the examples, is currently in progress.