Heri,
I don't have any solutions to offer you at this time. Schema evolution
is definately a tricky problem. We're open to suggestions on how we can
tweak Castor to help solve these types of issues.
Thanks,
--Keith
Bender Heri wrote:
>
> Hi
>
> My server application which receives XML-Messages must treat 2 different
> specification versions of the XML-File. Most of the types, attributes and
> elements stay the same between the versions (98%) but some are different
> (mandatory/optional, existing/not existing, renamed elements).
>
> I thought of resolving this problem like this:
> - having 2 different schemas which include a third schema where the
> unchanged items are declared
> - let castor build the classes in two different subpackages
> - creating wrapper classes for each castor generated class which implements
> an interface
> - working only with the interface
>
> The problem is now, that there are really a lot of elements and types. I
> have to create for each castor generated class one interface and two
> wrappers (one for each version. Maybe I must support three or even more
> versions in future) -> much boring error-prone work.
>
> Is there annother way of addressing such an issue? I particular the common
> unchanged types and elements should be wrapped into the same class (not
> different classes with the same name in different sub packages).
>
> Heri
>
> BTW: Castor 9.5.2, java 1.4.2
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
