On Fri, Jan 28, 2011 at 4:08 PM, MAX STARETS max.star...@oracle.com wrote:
I just submitted a fix, so barring any new issues we do not have to require
that partial state saving be disabled.
Awesome, thanks for fixing this Max!
Wanted to mention that I suspect that we may have some more subtle
Hello Everyone,
It appears that both 1632 and 1635 were fixed for the case when view
root caching was disabled.
The exception from 1632 was still there when we were caching the view root.
I just submitted a fix, so barring any new issues we do not have to
require that partial state saving be
There was this
https://issues.apache.org/jira/browse/TRINIDAD-1632
On 1/26/2011 10:15 AM, MAX STARETS wrote:
Blake,
Andy and I have discussed this offline a bit, and his preference was we do not
hack the flag
to be off explicitly (he thought it would create even more confusion). He also
It looks like that was fixed, so is the problem now TRINIDAD-1635
https://issues.apache.org/jira/browse/TRINIDAD-1635.
-- Blake
On 1/27/11 2:18 PM, Gabrielle Crawford wrote:
There was this
https://issues.apache.org/jira/browse/TRINIDAD-1632
On 1/26/2011 10:15 AM, MAX STARETS wrote:
Blake,
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-namejavax.faces.PARTIAL_STATE_SAVING/param-name
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
I think we need to do both--essentially force partial state saving off
and document that we are going to force it off.
-- Blake Sullivan
On 1/26/11 6:57 AM, Matthias Wessendorf wrote:
On Wed, Jan 26, 2011 at 3:33 PM, MAX STARETSmax.star...@oracle.com wrote:
Hello Everyone,
I think we need
Blake,
Andy and I have discussed this offline a bit, and his preference was we
do not hack the flag
to be off explicitly (he thought it would create even more confusion).
He also suggested that we look
at fixing the issues in Trinidad sooner rather than later. The users are
getting the
