Seam by default is going to start on conversation when the page loads initially, you simply control whether the conversation is promoted to long-running. If not the conversation is destroyed once the request completes. You could tell Seam to always promote the conversation to long-running when you company information screen is accessed through pages.xml (there are other ways of doing this as well): <page view-id="company-information.xhtml" action="#{conversation.begin}" /> Then on the submit method: | ... | @End | public void submit() { | // do submit | } | ... which would end the long-running conversation regardless of whether the company-address view was accessed or not. This also helps if you have edit scenarios where you have to edit company information. You would definitely want to start a long-running conversation as soon as the data is loaded for editing on access of company-information.xhtml so you can maintain the state of your company instance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086761#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...