Multiple calls to a conversation with explicit id cause the multiple execution of the @Begin method --------------------------------------------------------------------------------------------------- Key: JBSEAM-976 URL: http://jira.jboss.com/jira/browse/JBSEAM-976 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA, 1.1.7.CR1, 1.1.6.GA, 1.1.5.GA, 1.1.1.GA Environment: Seam 1.2.0Patch1 + Facelets on jBoss AS 4.0.5 GA Reporter: raffaele camanzo The situation described in the summary is different from the behaviour defined in the documentation (ref. 6.6): "Clearly, these example result in the same conversation id every time a particular hotel, blog or task is selected. So what happens if a conversation with the same conversation id already exists when the new conversation begins? Well, Seam detects the existing conversation and redirects to that conversation without running the @Begin method again. This feature helps control the number of workspaces that are created when using workspace management." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira