On Tuesday 12 October 2010 9:12:09 am Benson Margulies wrote: > After a long period of hibernation, I am now pushing toward a > releasable version of XmlSchema 2.0. I have plugged it into CXF and am > working out the kinks. > > Xml Schema 2.0 will be materially different than the current branch. > Superficially, it uses standard Java 1.5 generic collections and > enums. More deeply, objects reference back to their containing > schemas, and the top-level collections in the schema are > self-maintaining. > > If any of you who integrate XmlSchema into other projects want to > influence this, it would be a good time to have a look. Of course, it > would have been a better time last year when I was committing the bulk > of this, but there's certainly a possibility to make adjustments now.
I just started working a bit more with this to help Benson with some of the CXF kinks and I must say I like a lof of this. A bunch of our loops and such are much nicer. A BUNCH of utility junk we had just goes away. Quite nice. :-) One big heads up to be aware of is the behavior of XmlSchemaElement.getQName() is very different now. In the older versions, that returned the QName of what it would look like on the wire. For example, in unqualified schemas, the namespace would be empty. With 2.0, the QName of the element is really the full qname of the element. That's actually really nice, but a big behavioral difference. There is a separate getWireName call that would return the qname of what the element would look like on the wire. -- Daniel Kulp dk...@apache.org http://dankulp.com/blog
