[
http://jira.jboss.com/jira/browse/JBSEAM-95?page=comments#action_12341884 ]
Raja commented on JBSEAM-95:
----------------------------
This also happened in a Stateful Bean where the producer and consumer of an event are in
the same stateful bean. Once the event got fired, the Container started another thread for
the consumer of the bean leading to the "concurrent access to stateful bean"
Have Seam handle "concurrent access to stateful bean"
exceptions elegantly.
---------------------------------------------------------------------------
Key: JBSEAM-95
URL:
http://jira.jboss.com/jira/browse/JBSEAM-95
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Affects Versions: 1.0 beta 1
Reporter: ryan dewell
See the rejected issue: EJBTHREE-313
This can be duplicated in the demo app (or any other app), by simply double clicking a
commandLink/commandButton. If Seam could detect the double postback, and just ignore one
of them, that would be ideal. Perhaps JSF 1.2 provides better postback detection
handling?
--
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