The way I see it, no transaction should span more than a single request or form submission
on the webapp. In read/modify/write cases we should (if we have not already) adopt an
optimistic locking style of strategy, where we trigger an error on form submit if the
relevant server state has changed between the request of the form and the submission of
the same form.
That said, I don't see why we can do whatever we want with transations, at least with
respect to the web application.
My apologies if I'm duplicating what you've already said.
Also, I don't really like the idea of keeping a heavyweight state on the web
application side either. Ideally the web application would be purely stateless. Of
course this may or may not be possible - I'm still not familiar enough with the API to
know for sure. Working on it though!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967872#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...