JiBX 1.1.5

JiBX is a framework for binding XML data to Java objects. JiBX project lets you work with data from XML documents using your own class structures. The JiBX framework handles all the details of converting your data to and from XML based on your instructions.
JiBX is designed to perform the translation between internal data structures and XML with very high efficiency, but still allows you a high degree of control over the translation process.
How does it manage this? JiBX uses binding definition documents to define the rules for how your Java objects are converted to or from XML (the binding). At some point after youve compiled your source code into class files you execute the first part of the JiBX framework, the binding compiler.
This compiler enhances binary class files produced by the Java compiler, adding code to handle converting instances of the classes to or from XML. After running the binding compiler you can continue the normal steps you take in assembling your application (such as building jar files, etc.). You can also skip the binding compiler as a separate step and instead bind classes directly at runtime, though this approach has some drawbacks.
The second part of the JiBX framework is the binding runtime. The enhanced class files generated by the binding compiler use this runtime component both for actually building objects from an XML input document (called unmarshalling, in data binding terms) and for generating an XML output document from objects (called marshalling). The runtime uses a parser implementing the XMLPull API for handling input documents, but is otherwise self-contained.
Enhancements:
- Corrected a pair of problems with nested unordered groups, which resulted in exceptions during code generation.
- Fixed the "j2me" target for building under Windows.
- Changed child component order under < binding > element to namespace, format, include; corrected binding.xsd, binding.dtd, and documentation to match.
- Extended < include > support to allow < format > definitions from included bindings to be used within the including binding, and to support namespace scoping (global namespaces within the including binding apply to all included bindings; global namespaces within included binding apply only to that binding)
- Fixed handling of abstract < mapping > with attributes (with or without content).
- Added check for abstract class used directly (needs factory-method).
- Loosened checks for element name on child components of collection to only test < value > element children.
- Fixed problem with abstract base mapping use in unordered collection failing code generation (stack size mismatch).
- Corrected a problem in working with arrays of longs or doubles which could result in modified classes failing JVM validation.
- Corrected handling of optional mapping references.
- Changed default JiBX build Ant target to build the full distribution with debug information included, added a new "small-jars" target to compile and jar without debug information.
- Added propagation of namespaces defined in abstract < mapping >s up to the context of each reference to those < mapping >s.
- Fixed add-constructors=true option to make existing default constructors accessible, and to add superclass default constructors where necessary.
- Fixed handling of abstract < mapping > with no content or attributes present
- Removed erronous warning message about default used without usage=optional (default actually implies optional)