As I understood you are looking for an databinding framwork which does not
do any validation. try jaxb.
On 4/16/07, Josh <[EMAIL PROTECTED]> wrote:
Amila,
If I configure a databinding approach to work with the following XML:
<person>
<firstName>John</firstName>
<lastName>Doe</lastName>
</person>
Which databinding approaches will not break if I pass in the following
XML:
<person>
<firstName>John</firstName>
<lastName>Doe</lastName>
<age>25</age>
<sex>M</sex>
</person>
While most client applications may not want to interpret the new
information, I want to make sure that I can recommend a binding approach
that does not cause a ripple effect when new items are added to the schema.
Does this clarify what I am looking for?
-Joshua
On 4/16/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
>
>
>
> On 4/14/07, Josh <[EMAIL PROTECTED] > wrote:
> >
> > All,
> >
> > I am looking to determine which client side data binding choices
> > (castor, jibx, jaxb etc) allow backwards compatible schema changes (eg
> > addition of a new field) without throwing an exception.
> >
>
> What you exactly mean by backword compatible schema?
> e g. if you add a new element to a complex type with minOccurs 0 then
> this should work properly with the requests you got earlier as well. But in
> this case it the way you write schema and it has nothing to do with the
> databinding frame work as far as it correctly interpret the schema.
>
>
> I am hoping to recommend some solutions to my clients that would allow
> > me to make backward compatible schema changes without causing a ripple
> > effect. Has anyone come across this information?
> >
> > Regards,
> >
> > Joshua
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
--
Amila Suriarachchi,
WSO2 Inc.
