1. Two ways to enable Change Summary for static Data Object:
1.1 Use DataGraph
1.2 (preferred) add
<xsd:element name="changes" type="sdo:ChangeSummaryType"/>
into XSD before classes generation. The element name can be different.
2. Change Summary is supposed to have sufficient info to apply changes.
Change Summary will be serializable (
https://issues.apache.org/jira/browse/TUSCANY-1082)
Each ChangeSummary.Setting can be applied to a DataObject:
((FeatureChange)changeSummarySetting).apply((EObject)dataObject)
That's not in the spec...
On 1/29/07, Scott Kurinskas <[EMAIL PROTECTED]> wrote:
Hi Everyone,
Two basic questions (I hope), so please bear with me.
1. I was trying to use classes generated by the XSD2JavaGenerator
utility,
but could not find a way to enable change summary. Using generated
classes, is it possible to utilize change summary capabilities?
2. Is there sufficient metadata in ChangeSummary.getChangedDataObjects()
method to apply changes? As ChangeSummary is not serializable, I'm
looking
for alternatives. What I'm ultimately trying to accomplish is to utilize
SDO as a means of propagating changes between distributed system members.
Change summary seems to be well suited for this, but I'm stumped about how
to apply the changes if the base object contains thousands of entries (a
List). I've figured out the APIs to determine what has changed and more
or
less how its changed, but where to apply the change is the question.
In my testing, I have a fairly basic XSD that has an array of a complex
type.
Regards,
Scott
--
Yang ZHONG
