I reported this problem, but we found that the real cause was the
incompatibility between MyFaces 1.2.2 + Tomahawk 1.1.6, and RichFaces
3.1.2 SP1. When we switched to RichFaces 3.1.4 GA, the problem with
t:saveState disappeared.
Therefore, I won't open issue, since it is not a Tomahawk's problem.
Regards,
Ognjen
Martin Marinschek wrote:
Could you guys open an issue with a small sample app reproducing the issue?
regards,
Martin
On Thu, Feb 21, 2008 at 9:50 PM, Zheng, Xiahong <[EMAIL PROTECTED]> wrote:
Was there any resolution on this problem? I start seeing problem as well
with MyFaces 1.2.2 and t:saveState. If I switch to RI 1.2, everything
works fine.
-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz
Sent: Tuesday, February 12, 2008 6:02 AM
To: [email protected]
Subject: Re: [core] MyFaces 1.2.2 and t:saveState problem
<context-param>
<description>Define partial state saving as
true/false.</description>
<param-name>javax.faces.PARTIAL_STATE_SAVING_METHOD</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<description>Only applicable if state saving method is "server" (=
default) and if
org.apache.myfaces.SERIALIZE_STATE_IN_SESSION is
true (=
default) If true (default) the serialized state
will be
compressed before it is written to the session.
If false the
state will not be compressed.</description>
<param-name>org.apache.myfaces.COMPRESS_STATE_IN_SESSION</param-name>
<param-value>true</param-value>
</context-param>
Ognjen Blagojevic schrieb:
> Hi Werner,
>
> I didn't change anything in the webapp configuration. I just replaced
> MyFaces 1.2.0 jars (and dependencies) with 1.2.2. Where are savestate
> optimizations configured, and how do I turn them off?
>
> Regards,
> Ognjen
>
> Werner Punz wrote:
>> Werner Punz schrieb:
>>> Ognjen Blagojevic schrieb:
>>>> Hi all,
>>>>
>>>> I have MyFaces 1.2.0 + Tomahawk 1.1.6 webapp that works fine. I use
>>>> mostly request scoped beans, in order to keep the server memory
>>>> free. I'm also using t:saveState tag, when there is the need to
>>>> preserve the data for h:dataTable (as described on [1]). Parameters
>>>> are passed using
>>>>
>>>> <f:attribute name="isSomething" value="#{row.idSomething}"/>
>>>>
>>>> However, when I try to switch to MyFaces 1.2.2, t:saveState shows
>>>> unexpected behaviour. It seems that when MyFaces evaluates
>>>> expression row.idSomething, it doesn't consult the data that is
>>>> saved for the last time with the t:saveState, but the one that is
>>>> older, and therfore invalid.
>>>>
>>>> Any ideas on this one?
>>>>
>>> Sounds like a bug to me, do you have the savestating optimizations
>>> turned on?
>>>
>> To clarify things, to my knowledge some savestate optimizations went
>> in 1.2.2, maybe there still is a bug there, you might try to turn
them
>> off if you have turned it on.
>>
>> Werner
>>
>>
>
>
