Action annotated with @Begin(nested=true) does not actually execute within the nested conversation -------------------------------------------------------------------------------------------------- Key: JBSEAM-1259 URL: http://jira.jboss.com/jira/browse/JBSEAM-1259 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Michael Youngstrom If I have a method annotated with @Begin I would expect that method to be executed inside of the conversation it is beginning. This is the case for a top level conversation however if beginning a nested conversation "@Begin(nested=true)" the method is not executed within that nested conversation because the nested conversation is not started until after the method returns. Conversations probably function this way because of the "ifOutcome" attribute. However, I believe it introduces unexpected behavior in the case of nested conversations. For example, I have an action that starts a nested conversation and loads data that I only want to be available for the scope of the current nested conversation. Any conversation variables I create in the action are actually created in the outer conversation and not in the new nested conversation because the nested conversation is not actually created until after my action executes. Options: Perhaps for nested conversations we can begin the conversation before calling invocation .proceed in the ConversationInterceptor and then end the conversation if "ifOutcome" is not satisfied? Any other ideas? Mike -- 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