[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2501) Action not being called on backing bean in default scope.
9:35 p.m.
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
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
9:37 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=all ]
Mark Richter updated JBSEAM-2501:
---------------------------------
Attachment: booking.zip
Attachment of modified booking example files that demonstrate the issue.
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
7:38 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=all ]
Pete Muir closed JBSEAM-2501.
-----------------------------
Resolution: Rejected
Please pursue support issues on the forum.
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
4:33 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ 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
4:38 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=all ]
Pete Muir closed JBSEAM-2501.
-----------------------------
Resolution: Rejected
Don't reopen rejected issues.
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
4:41 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=comments#action_12402271 ]
Pete Muir commented on JBSEAM-2501:
-----------------------------------
Start a topic on the forum. Clearly explain your use case and problem. Show your changes
to the booking example in diff format. Don't threaten and don't exaggerate.
Then someone might help you.
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
4:29 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ 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
4:30 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=all ]
Christian Bauer updated JBSEAM-2501:
------------------------------------
Comment: was deleted
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
11:23 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=comments#action_12402627 ]
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
2:43 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=all ]
Christian Bauer updated JBSEAM-2501:
------------------------------------
Comment: was deleted
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
7:03 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=comments#action_12402669 ]
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
7:32 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2501) Action not being called on backing bean in default scope.
[ http://jira.jboss.com/jira/browse/JBSEAM-2501?page=all ]
Christian Bauer updated JBSEAM-2501:
------------------------------------
Comment: was deleted
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
6130
days inactive
6187
days old
11 comments
3 participants
participants (3)
-
Christian Bauer (JIRA) -
Mark Richter (JIRA)
-
Pete Muir (JIRA)