Sorry realized I probably didn't answer your question...We probably
also need to remove by UUID only if the entire conversation ends...I
need to add that.
Jim
On Nov 21, 2006, at 3:04 PM, Jim Marino wrote:
Hmm, not sure I see it. There is a removeRecord op by owner and id.
But I don't see a removeRecord op by id only.
The unique id of the instance needs to be a combination of the UUID
and owner since multiple instances can be stored with the same
UUID. For example, conversations involving local services have the
conversation id (UUID) propagated so we could wind up with multiple
instances persisted for each UUID. In the memory store case, we can
key off the actual owner instance since everything can be located
object identity. However, in the durable case we need to be able to
reconstitute owner identity during recovery. The best way I could
think of doing this is to calculate the canonical name of the SCA
object by walking its ancestors (this is only done once per SCA
Object or AtomicComponent so it should be cheap) since this will
never change unless there is a change in the composite implementation.
Jim
---------------------------------------------------------------------
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]
