[
https://issues.apache.org/jira/browse/MYFACES-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533628
]
Michael Kurz commented on MYFACES-1733:
---------------------------------------
You're right, it is not a special link but MyFaces got confused with the
combination of this link and the request parameter with server-state-saving
enabled.
Restore view is just the name of the first phase in the JSF lifecycle.
> [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.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6-SNAPSHOT
> Reporter: Stephen Friedrich
> Priority: Critical
> Attachments: jira1733-patch.zip
>
>
> 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.
