Yes, the server will not be able to detect if the view is rendered to a new window. But if the conversation context is stored in the client, the server does not need to know. If a user opens a view in a new window the context is sendt to the server along with the request, the request is handled, new data is set in the context and the view is rendered to the new browser tab. If the "old" tab sends a different request (for example without opening a new tab), the server handles the "old" context without knowing that it was the same as the previous context. The context data is just set during the application phase, and the response is sendt back to the browser. In effect that means that we have split one conversation in two... I thought i could accomplish this with client side conversations (core:init client-side-conversations="true"), but i suspect the conversation id parameter that always is appended somehow makes seam set the different conversation contexts as part of the same conversation (which is of course the expected behavior) Maybe one could turn the conversation id parameter off? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081261#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...