This is a *very* desirable goal, but it's going to be tough to address
schema evolution issue in JAXB2 specification when XSD specification
itself makes it nearly impossible. As Noah Mendelsohn wrote recently,
W3C XSD WG is well aware of problem and is considering options to fix
it. He also wrote one proposal:
http://lists.w3.org/Archives/Public/www-tag/2004Aug/att-0009/NRMVersioni
ngProposal.txt
Thanks,
George
> -----Original Message-----
> From: Ian Poccachard [mailto:ipocca_at_blueyonder.co.uk]
> Sent: Monday, November 01, 2004 9:07 AM
> To: users_at_jaxb.dev.java.net
> Subject: Schema evolution in JAXB 2.0
>
> Hi guys,
>
> I am interested to know more about the views of the expert
> group regarding schema evolution.
>
> I checked out the JAXB 2.0 Early Draft v0.4 June 10, 2004.
> Section 1.2 lays out the goals, item 7 refers explicitly to
> schema evolution.
>
> Can someone give an informed view of what is likely to be
> available say by the end of 2005? The early draft was a little vague.
>
> Regards
>
> Ian
------------------------------------------------------------------------------
This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation.
====================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net