Hi Folks,
We're readying a CRM application that uses Seam heavily, and are going through some of
our lingering issues, one of which is the current access to stateful beans problem.
I've found first mention to it here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70595
It's attached to a rejected JIRA issue here:
http://jira.jboss.com/jira/browse/EJBTHREE-313
I tend to agree that Seam is trying to do something here that the EJB3 spec does not
allow. It would be most useful for us if Seam could serialize the requests so that they do
not hit the same component concurrently when the user gets impatient and clicks links
twice, or (painful) double-clicks everything in the UI.
Is/has this been addressed? Is there a JIRA issue I missed that covers this?
I suppose we could pretty up the exceptions, but I'd really rather have a proper
solution.
We're currently using Seam 1.0.1.GA and JBoss 4.0.4.GA with EJB3 RC8.
Thanks!
Steve
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958547#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...