That's because the conversation is created in the first request, and if you delay the response then the remoting client won't know which conversation id was created. One alternative is to start your conversation when you first render the page and manually set the conversation id like this:
| Seam.Remoting.getContext().setConversationId(#{conversationId});
|
That way the remoting calls will know which conversation context to use.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021423#4021423
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021423
ooops!
Sorry, after another try it worked!
I messed up with the pages.xml files of versions 1.1.6.GA and CVS of 02-18-2007.
As soon as the request parameters are defined in
<page view-id="/comment.xhtml">
| <restrict/>
|
| <param name="name" value="#{selectedMember.memberName}"/>
| <param name="blogId" value="#{selectedBlog.blogId}"/>
|
| <navigation from-action="#{blog.saveComment}">
| <redirect view-id="/blogentry.xhtml"/>
| </navigation>
| </page>
it works fine.
Thx.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021414#4021414
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021414