Slide J2EEStore and Managed Transactions in App Server

[Willie Vu <ct...@ust.hk>]

Dear Remy and Michael,

Under desperation, I hope you could offer some insight on how to get Slide
J2EEStore working in app server such as JBoss.  The problem is about
transactions.

There are a couple of threads detailed the problems of using J2EEStore in JBoss:

http://marc.theaimsgroup.com/?l=slide-user&m=104323035513276&w=2

http://marc.theaimsgroup.com/?l=slide-user&m=105411767813227&w=2

I want to know, in particular, how the Slide's transaction manager works with
app server's own transaction manager?  Can they co-exist and manage the same
connection objects?  If the app server's TM has to manage the connections,
should the Slide's TM be disabled, or should a new store be created so that the
new store does not take part in the management of Slide's TM?  In other words,
the new store will make use of a connection from the app server as if it is a
data access object and nothing more.  It does not do any explicit transaction
operations such as commit, rollback.  The new store lets the callers of Slide
API to manage transactions.  There are 2 callers in J2EE container - EJB and
servlet.  EJBs can use container-managed transaction (CMT) or bean-managed
transaction (BMT).  Since the Slide TM is not involved, JBoss' TM will happily
manage transactions.  If servlets call Slide API directly, they are like BMT
EJBs.  They need to get a UserTransaction and wrap around Slide API calls within
UserTransaction's begin() and commit()/rollback().

Will the new store work?  Will it screw up Slide's TM?

Thank you in advance.


--
Willie Vu


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org