[
https://issues.apache.org/jira/browse/MYFACES-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898665#action_12898665
]
Werner Punz edited comment on MYFACES-2881 at 8/15/10 6:22 AM:
---------------------------------------------------------------
HI, I will patch something in with my next commit, which will probably come on
monday.
For Trinidad and richfaces, I guess they have their own fixup code either in a
listener, or by altering the partial response and adding their own stuff (which
is more likely)
But as I said, you might run into the same issue with Mojarra, they simply only
update
other forms if they ar parts of their render targets. I did a testing and could
reproduce the issue there.
Anyway once the code is in I will drop the explanation for it here, I will
reopen the issue again.
Addendum: There is a way to fix it for both impls, here is the deal, first I
will enable the updateallforms mechanism for myfaces, but I will drop a code
snippet here which will add a listener which fixes it for both impls. So expect
all of this on monday probably around the afternoon. Mojarra does not have this
fixed, so fixing it from the outside with a listener might be the cleanest way,
but that does not really prevent me from enabling it via a config param in
myfaces from the inside.
was (Author: werpu):
HI, I will patch something in with my next commit, which will probably come
on monday.
For Trinidad and richfaces, I guess they have their own fixup code either in a
listener, or by altering the partial response and adding their own stuff (which
is more likely)
But as I said, you might run into the same issue with Mojarra, they simply only
update
other forms if they ar parts of their render targets. I did a testing and could
reproduce the issue there.
Anyway once the code is in I will drop the explanation for it here, I will
reopen the issue again.
> Server state saving with two forms, ajax and normal request is broken
> ---------------------------------------------------------------------
>
> Key: MYFACES-2881
> URL: https://issues.apache.org/jira/browse/MYFACES-2881
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 2.0.1, 2.0.2-SNAPSHOT
> Environment: myfaces 2.0.1 or trunk;
> Reporter: Martin Kočí
> Priority: Blocker
> Fix For: 2.1.0
>
>
> Use simple xhtml with:
> <h:form id="form1">
> <h:commandButton value="Partial">
> <f:ajax execute="@this" render="@this" />
> </h:commandButton>
> </h:fom>
> </h:form>
> <h:form id="form2">
> <h:commandButton value="Full" />
> </h:form>
> then:
> 1) click "Partial" button 20x or more
> 2) click "Full" button
> -> ViewExpiredException appears. If you click "Partial" 19 times or less
> ViewExpiredException does not appear.
> 20 is default for NUMBER_OF_VIEW_IN_SESSION - it you set this param to 1 you
> reproduce this problem with two clicks. Maybe there is more simple test case
> for reproducing this issue but I didn't find it yet.
> This bug is present in 2.0.1 already and is related to server state saving:
> myfaces 2.0.1:
> PSS + server: failed
> PSS + client: ok
> FSS + server: failed
> FSS + client: ok
> myfaces 2.0.2-SNAPSHOT:
> PSS + server: failed
> PSS + client: ok
> FSS + server: failed
> FSS + client: ok
> Very likely this causes MYFACES-2877 too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
