From: <jib...@li...> - 2005-07-27 22:20:36
|
I've just posted the RC1 release. I'm hoping to only make documentation changes at this point before the official production release. Major changes since RC0 include: 1. Corrected problems with <include> operation, and with binding model error detection for <includes> (passing context properly). 2. Modified JiBXException chained exception handling to work properly on JDK 1.3. 3. Fixed issue with finding set-method when no type otherwise specified (for input-only bindings). 4. Corrected issue with marshalling to UTF-16 encodings. 5. Various improvements and corrections for the binding validation, and to the handling of several unusual binding structures which resulted in IllegalStateExceptions during the binding compile. 6. Added the "force-classes" attribute to the <binding> element to force the generation of marshaller/unmarshaller classes for abstract non-base mappings (essentially type mappings), and the org.jibx.runtime.IBindingFactory.getTypeIndex() method to provide a way of looking up these type mappings at runtime. This was an incompatible change to the binding compiler, so it requires rerunning the binding compiler for all classes bound with earlier versions of JiBX. 7. Solved a problem where the Ant build would use the old version of the jars for some tests when running a target which both rebuild jars and ran tests (the problem was the "bind" task definition at the top level of the build.xml, which would attach to the old version of the jars). 8. Added support for arrays as collections. 9. Added "choice" attribute to mapping and structure definitions, which generates code to accept one and only one of the child components (which must all be elements) when unmarshalling. 10. Added type names for abstract mappings, allowing multiple abstract mappings for the same class to be defined and referenced as needed. 11. Added requirement for value element child of collection to have type (either using type attribute of value element, or item-type on collection). 12. Added QName value type to extras, QNameReference example in test/extras to show handling namespace declarations using pre-get and pre-set methods. 13. Fixed problem with wrong element name reported when the expected name for elements in a collection is not found. 14. Improved source tracking to avoid common problems with location being set multiple times (causing reported location to be off). 15. Corrected issue with pre-set methods only being called when a new instance of the object was created. - Dennis |