Phrased differently, I guess this would be the idea of a conversation "home". Or, the idea of more control over conversation resuming...
Perhaps by default Seam could simply use the very first ViewId associated with a conversation as the "home" view ID. Then, a new option in @Begin could be: resume=ResumeType.CONVERSATION_HOME or something like it. Another implementation approach that might serve a slightly different purpose would be a new annotation called @Resume. Seam would call this method when it was getting ready to resume an explicit conversation. The outcome could be run through the regular JSF navigation handler and the appropriate home view could be determined that way. Returning null means that Seam uses the existing view ID assigned to the conversation. Thus, the application gets to control if the current view is kept or changed, and if any other logic is run before resuming. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953111#3953111 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953111 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
