This content has been marked as final.
Show 3 replies
-
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
-
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.
-
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