"jason.greene(a)jboss.com" wrote :
| So the big difference here is that unlike JBossXB, there is no way to override the
java annotations with schema annotations. This loss of flexibility is for performance
reasons (no need to read/parse the schema at runtime).
|
So this creates a problem if the object model needs to be fixed (public API etc), but the
schema needs to change significantly. Or different schemas need to be associated with the
same object model. Under these scenarios, it's better to use the JAXB object model as
an intermediary that directly represents the xml (in object form), and then copy / merge
this information into a more elegant public API.
-Jason
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006588#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...