Robbie, yes, some DASs may implement a polocy where the graph returned is already logging, but we don't have a DAS here, and ChangeSummary is part of the SDO API, so it's perfectly valid, and necessary in the absence of a DAS, to expose this to the user here. You may like to make a comment that in a real situation, depending on how the graph was received it may or may not already be in a logging state.
Cheers, Kelvin. On 7/12/06, Robbie J Minshall <[EMAIL PROTECTED]> wrote:
Kelvin you mentioned that : > In think there's some missing code in this example, in that logging needs to > be turned on to get the serialization to include a populated change > summary. I am unsure about this. My understanding was that the use of beingLogging and endLogging was handled by various DAS implementations and essentially hidden from the end user of the DataObject. How should this work ? What roles should be using the ChangeSummary.begin/endLogging methods ?
-- Best Regards Kelvin Goodson
