AJAX UI -> (via GWT RPC) -> composite-scoped service (C1) -> conversation-scoped service (C2)
Now I want that each call made from one session will go to one C2 instance, and calls made from different session (with different session id) will go to different C2 instance. I’ve tried to extract session id in my GWT-RPC binding and put it as a “conversationID” in the “from” field of Message which I use to invoke the C1, but this does not work as expected. Every time I have different C2 instance.
So, I want it to work the same way as referencing session-scoped bean from the singleton-scoped bean works in Spring framework.
Mike Edwards wrote:
Ivan Dubrov wrote:Hi,Is that possible to refer to the CONVERSATION-scoped component from COMPOSITE-scoped?What I want to achieve, is to make singleton component (COMPOSITE-scoped) retrieve some session data (which I want to model as a CONVERSATION-scoped component) during the request processing.Ivan, Yes, this should work fine.I assume that your conversation scoped component has a conversational interface of some kind? If this is the case, then when the composite scoped component calls it, a new conversation will be started with the comversation scoped component and the composite scoped component can continue to use this until the conversation session is explicitly ended (eg by calling an @EndsConversation method.)Yours, Mike.
-- WBR, Ivan S. Dubrov
signature.asc
Description: OpenPGP digital signature
