[
https://issues.apache.org/jira/browse/MYFACES-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533421
]
Mario Ivankovits commented on MYFACES-1733:
-------------------------------------------
I don't see how this patch will fix this issue. Did you try it?
facesContext.getExternalContext().getRequestParameterMap().isEmpty() retruns
true only if there is no GET NOR a POST parameter.
So in case of a postback you'll have at least the minimum view state required
to lookup the view state on the server - you'll always have at least one POST
parameter, except if you access a view directly, but then there is also no
STANDARD_STATE_SAVING_PARAM.
But maybe I miss something here?
Sorry then ;-)
> [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.
