Remoting and Conversation Scope

samdoyle Oct 1, 2008 7:27 AM

Hello,

I have been trying to get a remoting call work within the conversation scope. I have tried explicitly setting the conversation id for remoting as described in the documentation.

var cid = Seam.Remoting.getContext().getConversationId();
Seam.Remoting.getContext().setConversationId( cid );
Seam.Component.getInstance( "handler" ).trackChange( targetElement.id, newValue, oldValue, remoteCallback );

I have also tried:

Seam.Remoting.getContext().setConversationId( "#{conversation.id}" );

I continuously see a new instance of my conversaton scoped component being created.

Thanks for your time.

1. Re: Remoting and Conversation Scope

cretz Mar 26, 2009 5:47 PM (in response to samdoyle)

I too am having the same problem but w/ a page scoped component. It instantiates it every time, so local members of my bean are null. I'm using 2.1. The only way I've found to solve this is to use a session scoped component as a form of data storage and make sure it's page values are released on @Destroy of the page scope component
Actions
2. Re: Remoting and Conversation Scope

arnieoag Jan 12, 2010 5:11 PM (in response to samdoyle)

Have either of you discovered a solution? JBoss support isn't any help on this either.
Actions
3. Re: Remoting and Conversation Scope

nepoez.nepoez.gmail.com Jan 29, 2010 7:57 AM (in response to samdoyle)
get rid of the quotes of

Seam.Remoting.getContext().setConversationId( "#{conversation.id}"

and call the line right before your remoting call
Actions

Go to original post