Thanks a lot Mario. So, next step for me is following: I'm using Shale Dialog Manager that store dialog data in HttpSession in a Managed Bean with scope session. I don't know if I understood very well, but I'm going to fix Shale to store data in the current conversationContext. So I can have same dialog in differents windows. Do you think I have a chance of success? ( :) )
Thanks in advance Mario -----Original Message----- From: Mario Ivankovits [mailto:[EMAIL PROTECTED] Sent: 24 aprile 2008 15.03 To: MyFaces Discussion Subject: Re: [Orchestra] Explicit conversation starting and nested conversations Hi! > The user is inserting data for a Claim reading > from a paper, receive a call and start to insert a new Claim in a new > browser window (or tab). At the moment I have two browser using the same > HttpSession, the same function and same shared data and my application > does not work! > For this, with Orchestra, you have to have an outputLink e.g. "enter new claim" which is surrounded by o:separateConversationContext. This link must have a target="" (or any other trick) to open a new browser window. In this separate window then Orchestra will start a new conversationContext where you can have the exact same conversations running but with a different set of data. With Orchestra the scopes look like something like this: application->session->conversationContext->conversations Even if the conversation name is "enterClain", this conversation is separated between the conversationContexts. separateConversationContext does nothing else then stripping the conversationContext URL parameter from the URL, forcing Orchestra to start a new context. Ciao, Mario This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
