Bug 4241

Summary: Clarify when the Batch Container guarantees global transaction mode sematics
Product: jbatch Reporter: kmukher
Component: sourceAssignee: cvignola
Status: CLOSED FIXED    
Severity: normal CC: issues
Priority: P5    
Version: 1   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description kmukher 2012-10-26 19:05:17 UTC
In section 6.7.1 the spec states that the batch container will provide "global transaction mode semantics if and only if the services of a JTA-compliant transaction manager are made available to the batch runtime through use of the Transaction Management SPI." However, the "Otherwise the property is ignored," statement implies that the batch container will ignore the property if the given transaction manager is not JTA-compliant. 

Since there is no way for the batch container to verify if a transaction manager is JTA-compliant we should qualify the "ignore" statement with, "If the given transaction manager does not implement the TransactionManagerSPI the property will be ignored." I believe this make it clear that you can still provide a transaction manager spi implementation that is not JTA-compliant that will be used but that the batch container will not guarantee global mode semantics in this case.
Comment 1 cvignola 2013-01-16 15:30:31 UTC
The SPI is dropped.  The spec has been updated to clarify the use of global transactions.