[jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-2501) Action not being called on backing bean in default scope.

Mark Richter (JIRA) jira-events at lists.jboss.org
Tue Mar 11 17:33:08 EDT 2008

     [ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=all ]

Mark Richter reopened JBSEAM-2501:

I have tried everything mentioned in the forums and am unable to get this to work.  A quick search of the forums also provides a couple of other posts of people suffering this same issue but just don't know it.  A common question in the forums is "Why does the booking example use session scope?" (or similar).  These people hear Gavin's rant on how seam gets rid of putting everything in session scope and see that the examples just stick everything in the session.  I suspect I know why the booking example uses session scope... because of this bug.

A project I am working on is at a virtual stand still waiting on this bug and another $2M one that we are about to bid on will not use seam unless this bug is fixed.

> Action not being called on backing bean in default scope.
> ---------------------------------------------------------
>                 Key: JBSEAM-2501
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2501
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.1.CR1, 2.0.0.GA
>         Environment: Java 1.5.0_10, JBoss 4.2.2.GA, Windows XP, Seam 2.0.1.CR1
>            Reporter: Mark Richter
>         Attachments: booking.zip
> When you create a Stateful EJB in default conversation scope the action on a html commandButton is not always being called.  Also if you change it to a seam button the action is called however the forms fields are not being set.  This is best demonstrated with an example.  I will attach a modified booking example.  Simply replace the attached files with those in the seam booking example in 2.0.1.CR1 or 2.0.0.GA release.
> When you run the example, login (demo/demo) and click the find hotels button.  Now click the "Html - More results" commandButton.  All results are cleared because its defined action "hotelSearch.nextPage" is never called.  Put the bean in session scope and it works fine.  Also repeat this but this time click the "Seam - More Results" button.  When you click this button the action is called correctly however the setters (i.e. setPageNo, setSearchString etc..) are not called.  Apart from the inconsistency I would expect that in both cases the setters are called and then the action to be called.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list