myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Kurz (JIRA)" <>
Subject [jira] Commented: (MYFACES-1733) [Seam] Server-side state saving not working correctly
Date Tue, 09 Oct 2007 14:08:50 GMT


Michael Kurz commented on MYFACES-1733:

The problem seems to be that Seam uses a GET-Parameter for navigation. But those parameters
are only read by Seam if renderResponse is called in the restore-view-phase. This only happens
if no previous state is available (with client state saving) or if there are no POST- or GET-Parameters
at all (should happen for server state saving).

I provided a patch for 1.1.6 where renderResponse is called if there is no special view state
parameter. This should fix the server state saving problem with seam.

> [Seam] Server-side state saving not working correctly
> -----------------------------------------------------
>                 Key: MYFACES-1733
>                 URL:
>             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:
> 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>/ 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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message