The conversation should still exist, but I don't think instances in the conversation can be updated with the new component definitions. So, if you are updating the classes, you should generally consider the conversation to be dead.
BTW, Seam in Action is slightly misleading about the HTTP Session going away on redeploy. In JBoss, when you turn on HTTP session replication (even for non-clustered applications) then your session can be maintained between redeployments. When your app is redeployed, the session data is reloaded from the cache and you can keep going with the new code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122372#4122372 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122372 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
