Only a reminder, SDO changes are changes back to old state, not ones into new state.
E.g. a Property with value "old", after dataObject.set(property,"new"), now the Property value is "new", and the change is logged as "old". Applying the ChangeSummary.Setting to a DataObject will make its Property having value "old", not value "new". Previously I worked on Business Integration, which can propagate *new* changes between distributed system members. For the example above, value "new" is propagated, not value "old". Therefore apply method doesn't suit for that case. On 1/29/07, Scott Kurinskas <[EMAIL PROTECTED]> wrote:
Thanks (again) for you help. I'll give the below a shot. Regards, Scott On 1/29/07, Yang ZHONG < [EMAIL PROTECTED]> wrote: > > 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... >
-- Yang ZHONG
