Be aware that the W3C's versioning stuff, as in your link, is for allowing you to work with different versions of the XML Schema *specification*. I suspect that you want to work with different versions of a particular XML Schema, not different versions created using different versions of the specification.
To the best of my knowledge, XMLBeans does not provide any support for this. Versioning the namespace will work. If you wanted to keep the same namespace across versions but communicate the version information in the XML some other way, I think you would have to pre-parse some the XML (e.g. with SAX), determine the version, and then use a classloader to load the correct version. What I see people doing quite a bit now is to change the namespace only for new major (backward incompatible) versions. That way, if you use the latest minor version, it should be backwards compatible with previous minor versions and their shouldn't be an issue. If there is a backwards incompatibility, then the different namespaces allow you to manage that. Cheers, Tony. On 4 February 2010 18:49, cmoller <chad.mol...@gmail.com> wrote: > > Does XML Beans have a solution planned for XSD versioning beyond custom > class > loaders? Specifically, is there any plan to support > http://www.w3.org/2007/XMLSchema-versioning based versioning? > > I have control over the XSD that will be versioned, but I need to be able > to > accept files for older versions alongside new files. Are my only options a > custom class loader, versioning in the namespace, or versioning in element > names? > -- > View this message in context: > http://old.nabble.com/Support-for-versioning--tp27457786p27457786.html > Sent from the Xml Beans - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@xmlbeans.apache.org > For additional commands, e-mail: user-h...@xmlbeans.apache.org > >