For the next person that runs into this, I've got a work around. Say you have a frameset, frameset.jsp that has 2 frames, frameLeft.jsp and frameRight.jsp. Myfaces is not handling the state saving correctly (server-side), so the state will not be recovered for components inside frameLeft.jsp.
So get around this, you can make frameLeft.jsp itself a frameset that has only one frame inside. Inside that frame, put your actual view, and myfaces will recover the state correctly. Matt 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#a7931429 Sent from the MyFaces - Users mailing list archive at Nabble.com.
