Remote transaction support
--------------------------
Key: OPENEJB-1440
URL: https://issues.apache.org/jira/browse/OPENEJB-1440
Project: OpenEJB
Issue Type: New Feature
Components: container system
Affects Versions: 3.1.4
Reporter: Ed Staub
Provide transaction support in remote client (RemoteInitialContextFactory, et
al.)
In other words, doing a JTA lookup of java:comp/UserTransaction (at least) and
java:comp/TransactionManager (too?) will return a usable interface.
The client doesn't have to support participation of non-server datasources - it
just has to be able to start a transaction, check whether it's rolled back,
commit it, etc. This is provided by JOTM, JBossTS, and WebLogic, and probably
others as well.
Our server is slow to start up, and I'd like to be able to leave it running
while edit/debug-cycling transactional code that will eventually end up in the
server. The code all sits above other EJBs - no direct database calls. This
would also be a huge win in test development. We've found that stubbing out
transaction behavior leads to latent error-handling bugs - I don't want to just
provide a dummy them out.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
