I use this solution:
http://jira.jboss.com/jira/browse/JBSEAM-183
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959053#3959053
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959053
_
Yeah, in thinking further on this issue really serializing requests would be
evil.
What we really want to do is keep the browser from submitting subsequent
requests. Sounds like a JSF hack to me right now.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=395858
I actually managed to sneak something into the EJB3 spec at the last minute to
make it possible to detect a concurrentaccessexception. So the current issue is
here:
http://jira.jboss.com/jira/browse/JBSEAM-95
I suggest that you simply add your own handling for this exception in a servlet
filte