anonymous wrote : You may be able to use a combination of built in conversation components to help control the current/next conversation context programmatically. I actually looked into that and didn't see anything that jumped out at me. I suppose Conversation.leave() would probably be my best bet. If that unassociates the request from the current conversation then maybe the conversationId won't be added to the redirect. I'll give it a shot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957477#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...