[MYFACES-1733] [Seam] Server-side state saving not working correctly

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6-SNAPSHOT
• Fix Version/s: 1.2.2
• Assignee: Martin Marinschek
• Reporter: Stephen Friedrich
• Created: 27/Sep/07 07:26
• Updated: 16/May/09 03:35
• Resolved: 12/Oct/07 20:03

Description

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.

Issue Links

• relates to: MYFACES-2160 The action in tr:commandButton is not fired if you use the trinidad jsf library (in 1.1.5 it works).