ConversationContext issue

  • paoloRussian
Posted: Thu, 04/22/2010 - 09:16

In the bean I get the conversation context like this:

Context conversationContext = Contexts.getConversationContext();

if I put seam in debug mode, while calling the method via richfaces makes "conversationContext.session" be of datatype "SessionMap", while accessing the same method in Flex/flamingo leads to "ServletRequestSessionMap", and all the data inside it is .. well.. organized far from being usable.

My question is, since I have the correct conversation ID (set by SeamRemoteObject.setConversationId(xxx)), i have the "Conversation.instance()" on the server, and I only miss this damn "conversationContext" how can I extract this correctly when flamingo is doing the calls instead of richfaces??

This issue produces a NullPointerException in the code:

Context conversationContext = Contexts.getConversationContext();
IdataModel dm = (IdataModel)conversationContext.get(ObjectName); // <-- in flamingo calls there's nothing to get out of //context, then .. n.p.e.!

cheers and greetings to everybody here

I think is impossible

  • dkorotych
  • 04/15/10
  • Fri, 04/23/2010 - 07:41

Want you automatically receive server's ConversationContext in the client code? This is impossible. You can send the context as an ordinary object and restore it on the client. "Conversation support" in the Flamingo means the transfer of identificators (conversationId) between the client and server, but not objects