Bert,
This is part of the spec that IMO still needs a lot of work. Currently,
the spec doesn't really give a clear description of the change summary
serialization (not just the created objects), so implementations are
unlikely to interoperate. Right now, the Tuscany implementation doesn't
serialize the created objects ("create" attribute) at all, since the value
can be deduced from the serialized object changes (i.e., a parent
containment reference getting a new object that isn't also removed frorm
some other containment reference in the graph). Earlier, when we did
serialize it, we used a " " separator.
But, like I said, the spec is going to need to address this issue and
clearly define the standard serialization format before we will have
implementation interoperability.
Frank.
[EMAIL PROTECTED] wrote on 06/19/2006 03:50:38 AM:
> I've another q on the spec of ChangeSummary.
>
> The spec says:
>
> DataObjects which are currently in the data graph, but were not
> present when logging was started
> are indicated in the change summary with a create attribute
>
> <changeSummary create="E0004" >
> </changeSummary>
> ...
> <employees name="Al
>
> All nice and well, but what if there is more than one object created? Do
> you do it comma-separated then (just a plain guess) ? Or even worse, is
it
> up to the implementation to do something nice ...
>
> <changeSummary create="E0004,E005,E006"
> delete="#/a/b,E005,#/c/d/e" >
>
>
> Any idea why this is so underspecified, or did I miss something in the
> spec?
>
> Bert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
