You are right latest commit breaks that. I have committed a fix for that so it is working now.
2005/11/9, Vesa Lindfors <[EMAIL PROTECTED]>: > Mathias, > I tested successfully the rest of platforms with > javax.faces.STATE_SAVING_METHOD=server && > SERIALIZE_STATE_IN_SESSION=false && myfaces-20051030 . > > Now I should have time to continue testing your suggestion: > STATE_SAVING_METHOD=server && SERIALIZE_STATE_IN_SESSION=true && > myfaces-20051103. > But now my testing fails at the very begin: the application didn't worked > at all with state saving "server" - my ActionEvents weren't fired at all ( I > mean very basic form buttons didn't work anymore). Turning state saving to > the "client" it start to work again. I tried also with myfaces-20051107 and > same results. Do you have any idea what could be changed in NB during > 20051030- 20051103 so that it can have such effect? > > --- VLi --- > > > > > > > > >One more thing. I have removed the gzipping of the serialized stream > > >if server side state is used. This might have caused some additional > > >performance problems. Would it be possible to take the next nightly > > >(20051103) and test it again with > > >org.apache.myfaces.SERIALIZE_STATE_IN_SESSION=true to > check this? > > > > >Mathias > > > > -- Mathias
