Yes, it would be difficult if there was already a transaction in progress.
How about making this requirement only in the case where
TRANSACTION=SUSPEND and the task has started a transaction using the
UserTransaction provided but forgot to rollback or commit the
transaction when the task returns?
Regards
Anthony
On 2/21/13 1:56 PM, frowe_at_us.ibm.com wrote:
> I'm concerned about the "A task instance that starts a transaction but
> fails to complete the transaction is an error. The Java EE Product
> Provider is required to detect this error and abort the transaction."
> addition. I believe it should be the responsibility of the task to
> perform cleanup if the trans fails to complete because it has the most
> knowldege about what needs to becleaned up. Consider the case where
> there was already a transaction in progress
> (TRANSACTION=USE_TRANSACTION_OF_EXECUTION_THREAD), should the MES only
> roll back the part of the trans that failed in the task or all? How
> would it know?