[
https://jira.jboss.org/jira/browse/JBPM-1423?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1423:
-----------------------------------
standard java
===========
1) environment block controls the jdbc transaction through hibernate. hibernate being
one resource in the standard transaction.
2) user controls the jdbc transaction with hibernate and environment block has got to
participate in that same tx. Here, the tx will have a bigger scope then the environment
block. So special care should be taken to verify all usages of transaction-end-listeners
(like synchronisations)
3) user controls the transaction with spring and environment block has got to participate
in that same tx. Same comment: tx scope is bigger then environment block scope.
can we find a way so that the API tests are all executed in each of these 3 deployment
configurations ?
enterprise java
============
In enterprise Java, we can always assume that the transaction is controlled by JTA and
that the transaction has a bigger scope then the environment block. The most common case
will be CMT controls the transaction and pvm is addressed through the ExecutionService
local SLSB
osgi
====
testing only one of the tx configurations in osgi will be sufficient. To create a bundle
out of PVM, the
idenitfy supported deployments
------------------------------
Key: JBPM-1423
URL:
https://jira.jboss.org/jira/browse/JBPM-1423
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: PVM
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Priority: Critical
Identify the supported deployment environments and the corresponding configurations.
This basically will come down to transaction configurations in pvm, hibernate, spring,
ejb and the likes.
Configurations:
* pvm
* hibernate
* ejb
Controlling transactions:
* Hibernate transaction programmatic
* Direct JDBC connection programmatic
* JTA UserTransaction programmatic (== BMT?)
* CMT through EJB deployment descriptors
Also take given JDBC connections into account
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira