I replaced the existing conversational scope container with this new
parallel one (and removed the parallel one). This required the
ConversationalScopeObjectFactory to get a Store instance to pass
to the new instance of the scope container it creates. To achieve
this I autowired a Store constructor parameter and also added
a store component to system.scdl, implemented by MemoryStore.
Yep
This will probably need to change when the scope container also gets
a durable store instance.
Notice that when MemoryStore is autowired the loader throws an
IllegalPropertyException on getExpirationOffset, I commented out
the property annotation as I am not sure what the intent here is, I
will
raise a JIRA to track this.
I think it was a refactor error - I may have moved the order of
getters and setters around and left the annotation in place. I'll
take a look.
Since the scope container does not support init and destroy, some of
the original test cases that deal with life cycle were failing; I
commented
out the tests for inits and destroys in these tests:
- BasicConversationalScopeTestCase
- ConversationalScopeRestartTestCase, and
- ConversationalScopeInstanceLifecycleTestCase
Yes I mentioned in my email that I don't think these lifecycle
callbacks are valid for conversations (I'm trying to update the spec
to this effect) since if we have destroy, we will have to deserialize
any passivated instances to invoke @Destroy methods. This was a big
problem with EJB and I hope we can avoid it.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
