On Wed, Jan 26, 2011 at 3:33 PM, MAX STARETS <max.star...@oracle.com> wrote: > Hello Everyone, > > I think we need to do something about the fact that any Facelets application > with Trinidad 2.0 > will fail in a very non-obvious way unless partial state saving is disabled > with the following context > parameter: > > <context-param> > <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name> > <param-value>false</param-value> > </context-param> > > > I see two options: > > Document it prominently in the release notes > Try to "fake" the parameter in Trinidad code as always being set. > > I am not sure if (2) is feasible, but the advantage would be that the users > will not have to manually re-enable partial > state saving when we resolve the compatibility issues.
I am fine with (2), even if it's a bit hacky :-) > > Opinions? > > Max > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
