You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by sarathmavilla <sa...@in.com> on 2009/01/01 07:06:35 UTC

Re: using orchestra with jsf



Simon Kitching wrote:
> 
> Hi Sarath,
> 
> On Wed, 2008-12-31 at 02:46 -0800, sarathmavilla wrote:
>> hi,
>> iam new to myfaces orchestra and i dont know how to use it in my
>> application.
>> i search for samples of conversations, but i cant get it.
>> can u please give the samples how to use conversation in jsf application
>> with parent child conversations used in popup windows and tab windows.
>> 
>> i tried using beans with our own conversation scope.but i cant get the
>> values from popup windows to my main window.
>> 
>> where can i get the samples for this whole.
> 
> The "examples" module is listed on the orchestra website:
> http://myfaces.apache.org/orchestra/myfaces-orchestra-examples-project/index.html
> 
> There isn't much description there, but the "source repository" link
> points to here:
>   http://svn.apache.org/repos/asf/myfaces/orchestra/trunk/examples/
> from where you can download some examples.
> 
> As far as I remember, there aren't any examples dealing with multiple
> windows though.
> 
> When a new window (or browser tab) is opened, you need to make sure that
> the URL does NOT contain a "conversationContext" query parameter; the
> o:separateConversationContext tag can help with this.
> 
> The new window then runs in its own ConversationContext, ie it cannot
> access any of the conversation-scoped variables from the original
> window. Having two separate windows accessing the same conversation data
> has such nasty consequences that it is just better to avoid this
> completely.
> 
> So if you need to pass data "back" to the original conversation somehow,
> then you need to do it using some way other than modifying objects in
> conversation-scope. The way I usually do it is the old-fashioned
> approach of storing data as query-params in the URL.
> 
> Regards,
> Simon
> 
> 
> 
> 
> 
Hi Simon,

thnks for responding.
Can u tell me the simple way to get an existing bean in conversation ???

regards
Sarath
-- 
View this message in context: http://www.nabble.com/using-orchestra-with-jsf-tp21229709p21239490.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.


Re: using orchestra with jsf

Posted by Simon Kitching <sk...@apache.org>.
sarathmavilla schrieb:
> Simon Kitching wrote:
>   
>> Hi Sarath,
>>
>> On Wed, 2008-12-31 at 02:46 -0800, sarathmavilla wrote:
>>     
>>> hi,
>>> iam new to myfaces orchestra and i dont know how to use it in my
>>> application.
>>> i search for samples of conversations, but i cant get it.
>>> can u please give the samples how to use conversation in jsf application
>>> with parent child conversations used in popup windows and tab windows.
>>>
>>> i tried using beans with our own conversation scope.but i cant get the
>>> values from popup windows to my main window.
>>>
>>> where can i get the samples for this whole.
>>>       
>> The "examples" module is listed on the orchestra website:
>> http://myfaces.apache.org/orchestra/myfaces-orchestra-examples-project/index.html
>>
>> There isn't much description there, but the "source repository" link
>> points to here:
>>   http://svn.apache.org/repos/asf/myfaces/orchestra/trunk/examples/
>> from where you can download some examples.
>>
>> As far as I remember, there aren't any examples dealing with multiple
>> windows though.
>>
>> When a new window (or browser tab) is opened, you need to make sure that
>> the URL does NOT contain a "conversationContext" query parameter; the
>> o:separateConversationContext tag can help with this.
>>
>> The new window then runs in its own ConversationContext, ie it cannot
>> access any of the conversation-scoped variables from the original
>> window. Having two separate windows accessing the same conversation data
>> has such nasty consequences that it is just better to avoid this
>> completely.
>>
>> So if you need to pass data "back" to the original conversation somehow,
>> then you need to do it using some way other than modifying objects in
>> conversation-scope. The way I usually do it is the old-fashioned
>> approach of storing data as query-params in the URL.
>>
>> Regards,
>> Simon
>>
>>
>>
>>
>>
>>     
> Hi Simon,
>
> thnks for responding.
> Can u tell me the simple way to get an existing bean in conversation ???
>   

I'm not quite sure what you are asking here. Can you explain your
question more?

Regards, Simon