Just HEAD. I probably should start tagging versions at some point, but
haven't bothered so far.
- Dennis
Venkatesh Prasad Ranganath wrote:
Is this available off the HEAD in the CVS? Or is it available as a
tagged version?
On Wed, 2005-07-27 at 15:42 -0700, Dennis Sosnoski wrote:
I've just posted RC1, with a number of fixes and enhancements (more of
the latter than I'd originally intended). I'm hoping there won't be any
major fixes required to this one, so that I can turn it into a
production release by mid-August. The only change I *am* planning on is
rewriting some of the binding tutorial, including the part covering
collections (which is now hopelessly out of date).
Here's the list of major changes since RC0:
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
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
