each frame will have there own component tree (their own viewId) in the
server side..

                                                                           
             Matt Tyson                                                    
             <matthewcarltyson                                             
             @gmail.com>                                                To 
                                       [email protected]            
             12/15/2006 03:09                                           cc 
             PM                                                            
                                                                   Subject 
                                       Re: Saving State                    
             Please respond to                                             
                 "MyFaces                                                  
                Discussion"                                                
             <[EMAIL PROTECTED]                                             
                 ache.org>                                                 
                                                                           
                                                                           





Here is my theory.  When the request is submitted for the framed page, its
from the framing page, with a different session ID.


Matt Tyson wrote:
>
> I've got a component inside a frame.  The state is server side, and JSF
> can't find it.  If I hit a command button inside that frame, it can
> thereafter find the state.
>
> Leaving aside the question of why we are using frames, can anyone explain
> this behavior?  During the initial request for the page, the frame
> requests the viewId and I would therefore expect it to be saved.  This is
> the same viewId that is submitted by the command button...
>
> Thanks.
>
> Matt
>

--
View this message in context:
http://www.nabble.com/Saving-State-tf2828977.html#a7898365
Sent from the MyFaces - Users mailing list archive at Nabble.com.


Disclaimer: This electronic mail and any attachments are confidential and may 
be privileged. If you are not the intended recipient, please notify the sender 
immediately by replying to this email, and destroy all copies of this email and 
any attachments. Thank you.

Reply via email to