I prefer a more explicit approach. When you make a change
to a schema, the namespace for that schema should reflect
a new version.
The generated value objects should then reside in a different java
package.
something like this:
com.mycompany.package.v1
com.mycompany.package.v2
com.mycompany.package.v3
> -----Original Message-----
> From: Brett Porter [mailto:bporter_at_f2network.com.au]
> Sent: Sunday, November 10, 2002 10:39 PM
> To: JAXB-INTEREST_at_JAVA.SUN.COM
> Subject: Re: [JAXB-INTEREST] Schema versioning and
> schema evolution
>
>
> If you change the "source" version to include a new field, the
> "destination" code will still work, putting the extra
> field into a
> generic type (collection).
>
> Once the "destination" updates to the new schema def it
> will understand
> the new field. Or if you are using a generic mechanism
> to read out of
> the collection, it will understand it immediately.
>
> Cheers,
> Brett
>
> On Mon, 2002-11-11 at 15:03, Sam wrote:
> > Hi Brett
> >
> > Im m not sure I undertand what you're talking about.
> >
> > How will this help if the schema changes in its definition ??
> > /s
> >
> >
>