For a couple of reasons, @Conversational has not turned out to work very well in practice, so I've replaced it with a new mechanism which simply detects that a page was rendered inside a long-running conversation and blocks and redirects any actions originating from that rendered page if the conversation has ended. Clearly the question is "redirects to where?", and that is the bit I don't loive so much:
In pages.xml and pageflow definitions, you can now specify no-conversation-view-id to define where we should redirect to (a similar effect to ifNotBegunOutcome="...."). If anyone has better suggestions of where to define this, and a better name than "no-conversation-view-id", please speak up. The good news is that a bunch of problems with @Conversational are now gone. Eg, try refreshing a page from an ended conversation. This stuff is demoed in the DVDStore and booking demo. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954795#3954795 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954795 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
