You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@tuscany.apache.org by Daniel Peter <dp...@yahoo.de> on 2007/05/24 11:22:54 UTC
Evolution of a specific SDO structure over time
Hi all,
Assume there is a static generated SDO class, MySDO
edition1. Then an additional optional element is added
to the corresponding xsd, and thus the generated SDO
class, MySDO edition2, gets an additional property.
(At the time of the generation of MySDO edition1 it is
not known, where in the structure additional optional
elements might be added in the future.)
Is there a way that MySDO edition2 can be used for
Java serialization and the prior MySDO edition1 for
deserialization, and vice versa? (Of course with the
toleration of the potential loss of the information
held in the additional optional properties.)
Could the XML parser be configured to ignore unknown
xml elements?
Other options?
Thanks, Daniel.
__________________________________ Yahoo! Clever: Sie haben Fragen? Yahoo! Nutzer antworten Ihnen. www.yahoo.de/clever
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Evolution of a specific SDO structure over time
Posted by Frank Budinsky <fr...@ca.ibm.com>.
Hi Daniel,
I guess it would be OK, but the downside of making it a default option
(i.e., always do it) is that the SDO loader will then pretty much never
fail - you'll be able to load any junk without getting any load errors.
The other alternative is to expose the RECORD_UNKNOWN_FEATURE option as
one supported by Tuscany SDO, so you can pass it to the XMLHelper.load()
method when you want this behavior.
Comments? What do others thing about this?
Thanks
Frank.
Daniel Peter <dp...@yahoo.de> wrote on 05/25/2007 10:12:29 AM:
> Hi Frank
>
> It works if the following line is added to the
> configureXMLResource method of class DataObjectUtil:
>
> resource.getDefaultLoadOptions().put(XMLResource.
> OPTION_RECORD_UNKNOWN_FEATURE,Boolean.TRUE);
>
> Could you add this?
>
> Regards, Daniel.
>
>
>
> __________________________________ Kennt man wirklich jeden
> über 3 Ecken? Die Antworten gibt's bei Yahoo! Clever.
www.yahoo.de/clever
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Evolution of a specific SDO structure over time
Posted by Daniel Peter <dp...@yahoo.de>.
Hi Frank
It works if the following line is added to the
configureXMLResource method of class DataObjectUtil:
resource.getDefaultLoadOptions().put(XMLResource.OPTION_RECORD_UNKNOWN_FEATURE,Boolean.TRUE);
Could you add this?
Regards, Daniel.
__________________________________ Kennt man wirklich jeden über 3 Ecken? Die Antworten gibt's bei Yahoo! Clever. www.yahoo.de/clever
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Evolution of a specific SDO structure over time
Posted by Frank Budinsky <fr...@ca.ibm.com>.
Hi Daniel,
My guess is that the underlying EMF XML loader already has options to
support this. Someone (you? :-) just needs to figure out what options need
to be exposed to SDO clients, or even turned on by default, to make it
work in Tuscany.
Frank.
Daniel Peter <dp...@yahoo.de> wrote on 05/24/2007 05:22:54 AM:
> Hi all,
>
> Assume there is a static generated SDO class, MySDO
> edition1. Then an additional optional element is added
> to the corresponding xsd, and thus the generated SDO
> class, MySDO edition2, gets an additional property.
> (At the time of the generation of MySDO edition1 it is
> not known, where in the structure additional optional
> elements might be added in the future.)
>
> Is there a way that MySDO edition2 can be used for
> Java serialization and the prior MySDO edition1 for
> deserialization, and vice versa? (Of course with the
> toleration of the potential loss of the information
> held in the additional optional properties.)
>
> Could the XML parser be configured to ignore unknown
> xml elements?
> Other options?
>
> Thanks, Daniel.
>
>
> __________________________________ Yahoo! Clever: Sie haben
> Fragen? Yahoo! Nutzer antworten Ihnen. www.yahoo.de/clever
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org