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

Mark Richter (JIRA) jira-events at lists.jboss.org
Wed Mar 12 17:29:00 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=comments#action_12402597 ] 
Mark Richter commented on JBSEAM-2501:

That was not meant as a threat, I was just trying to point out how important this bug is to me and my company.

I spent the best part of half a day creating the code and docs for this bug and to have it treated with such contempt (not even looked at) is both frustrating and demoralising.  I guess I can be thankful that this happened before our up coming tender bid rather than during or after it.

> 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