I tried the following scenario: Page /object_details.xhtml is designed to show details of my particular object. I tuned pages.xml to map request parameters (such as objejctId) to properties of my SFSB backing the page. And my custom page action was marked as @Begin. I realized that in spite whether I'm using AJAX (IceFaces in my case) or not, Seam call that action method every time. So at the second attempt, when Seam tries to invoke action that is binded on a button on the page, it invokes @Begin method again and suggest annotating with @Begin(nested=true). That's a problem of Seam design - it provides us with myriads of possibilities, that are not working in combination some times :) In my case I succeeded with introducing a fake page that does nothing but accepting parameters and invoking page action. Page action method returns reference to another page. It helped me to omit reentering into new conversation. In other words you need to address your conversational page through the fake page, that does all preparation work for you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002259#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...