If any of the projects are exploring JAXB2 generated classes, then I think it is advisable to set the target to be "2.0" such that the generated classes can be usable with JAXB2.0.x and none of the JAXB2.1 leakages occur. I think JDK6 includes JAXB2.0.x I am no expert on JAXB2. But saw this while using the xjc command line tool. _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I do not think there is an answer to it apart from the fact that you can generate the classes into a single package. No other support. Here is the discussion that I started with no response. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=113388 Adrian wrote: > Yuck! Don't you have a create a whole new set of packages/classes for > ever change in the namespace/version? > > Or has JAXB fixed that now? > > How's anybody else supposed to programmatically use > your metadata if the classes change name with every release? > > On Tue, 2007-07-24 at 12:26 -0500, Anil Saldhana wrote: > >> If any of the projects are exploring JAXB2 generated classes, then I >> think it is advisable to set the target to be "2.0" such that the >> generated classes can be usable with JAXB2.0.x and none of the JAXB2.1 >> leakages occur. I think JDK6 includes JAXB2.0.x >> >> I am no expert on JAXB2. But saw this while using the xjc command line >> tool. >> _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

As to compatibility on schema updates, if you change the schema in a backwards compatible way its not a problem.

Adrian wrote: > On Tue, 2007-07-24 at 13:28 -0500, Jason T. Greene wrote: >> As to compatibility on schema updates, if you change the schema in a >> backwards compatible way its not a problem. > > You mean like changing the schema namespace from j2ee to javaee. ;-) Yeah, for that you would have to either regenerate classes, or alternatively change the annotations on all classes that refer to it. If you want something more dynamic, the Sun implementation does allow you to write your own "AnnotationReader", but this is not in the spec.