[
https://issues.apache.org/jira/browse/MYFACES-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530948
]
Stephen Friedrich commented on MYFACES-1733:
--------------------------------------------
It may well be that it is only Seam that triggers the bug - yet there is a
strong argument that the bug is in fact in MyFaces server-side state saving:
The problem goes away if you switch to either client-side state saving or use
the RI.
Martin, if you are familiar with MyFaces' server-side state saving it should
not be to hard to find the culprit.
I gave a reliable way to reproduce the problem - see above.
Matthias, here are some references to the problem (for what it's worth):
In previous versions of the Seam reference MyFaces was explicitly mentioned.
Now it's in milder form:
"Some JSF implementations have a broken implementation of server-side state
saving that interferes with
Seam's conversation propagation. If you have problems with conversation
propagation during form submissions,
try switching to client-side state saving."
The problems manifests in a couple of Jira issues, like this one:
http://jira.jboss.com/jira/browse/JBSEAM-1293
Gavin King:
"Right, this is a known bug in MyFaces. Nothing we can do about it, except get
off MyFaces and migrate to the RI (which we already did do)."
If you search the forum you'll find many people having problem with
MyFaces/Seam. Some of the posts are quite old, but the integration problem
still persists:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73933
[EMAIL PROTECTED]
"Right, this is a known limitation of using Seam with MyFaces, due to how
MyFaces does server-side state saving (I'm not going to call it an actual *bug*
in MyFaces, but it is suboptimal)."
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=106197
[EMAIL PROTECTED]:
"Don't use server side state saving, Seam, and MyFaces - it doesn't work. You
should use the RI 1.2 if you can - it's much better. You can use JSF 1.2 with
facelets in a 2.4 servlet container."
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=108488
[EMAIL PROTECTED]:
"Do not use server-side state saving with MyFaces, it's buggy. This has been
reported before (search the forum) and your problems with page parameters will
go away if you switch to client-side state saving or the JSF reference
implementation."
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=115728
[EMAIL PROTECTED]:
"There were known problems with server side state saving in myfaces. I think
you'll need to move to the JSF RI to make it work correctly with seam"
> Server-side state saving not working correctly
> ----------------------------------------------
>
> Key: MYFACES-1733
> URL: https://issues.apache.org/jira/browse/MYFACES-1733
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 1.1.5
> Reporter: Stephen Friedrich
>
> Sometimes when using server-side state-saving some state is fixed and won't
> ever update.
> I don't know how exactly this is caused, but it occurs a lot when using JBoss
> Seam.
> It is consensus in the Seam community not to ever use myfaces with
> server-side state saving or even better not to use myfaces, but the RI
> instead.
> Here is how to reproduce reliably with one of the Seam example applications:
> - download and unzip tomcat 5.5.
> - download and unzip JBoss Seam 1.2.1.
> - edit <seam-install-folder>/build.properties and specify the path to tomcat
> - edit <seam-install-folder>/examples/seampay/resources/WEB-INF/web.xml and
> change state saving method to server.
> - run ant deploy.tomcat from <seam-install-folder>/examples/seampay/
> - open http://localhost:8080/jboss-seam-pay
> - try to click on different accounts.
> => Only the first selection ever will make it. All others are ignored. Change
> back to client side state saving and everything works ok.
> I tried to look into this, but I am way over my head here with the internals
> of JSF and MyFaces.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
