> Your approach seems interesting. But I don't know if it would > be cleaner > to implement that kind of ASO and declare it in Hivemind. > Something like this: > > <state-object name="some-conversation" scope="conversation"> > <create-instance class="xxx.some.builder.class"/> > </state-object> >
Actually that's pretty much what I did. My previous explanations were a bit incomplete. Currently my setup in kickstart is as follows: a) I have one "special", session-scoped ASO, the current conversation, which is, basically, a Map, and an ASO-Manager which can be called to clean out the map (=terminate the conversation). This is a plain Tapestry ASO, no magic involved. b) Then I have a new ASO-scope "conversation", exactly as you propose. The corresponding ApplicationsStateManger stores its conversation-scoped ASOs in the session scoped conversation-ASO from a) c) And there' the PropertyPersistenceStrategy, of course. It's also called "conversation" ;) and stores its inhabitants in _the_ conversation-ASO from a) d) Finally there's a hivemeind service-model, somewhat inappropriately called "stateful" which stores a service in ... the conversation-ASO from a). So, it's really nothing new - just some wiring together - thanks to hivemind. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
