You may be able to use a combination of built in conversation components to help control
the current/next conversation context programmatically. This may interact better with
Seam's redirect filter (which is the guy that I think is adding your conversationId
param).
http://docs.jboss.com/seam/latest/reference/en/html/components.html#d0e6402
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957471#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...