You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@batchee.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2014/04/21 09:25:15 UTC
[jira] [Comment Edited] (BATCHEE-30) implement a
TransactionManagementService which uses UserTransaction
[ https://issues.apache.org/jira/browse/BATCHEE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975457#comment-13975457 ]
Romain Manni-Bucau edited comment on BATCHEE-30 at 4/21/14 7:23 AM:
--------------------------------------------------------------------
the main diff is: UT can check you are in the EE bean you looked up it from and fail if not.
last point: in jse providing a txmgr will be easier
was (Author: romain.manni-bucau):
the main diff is: UT can check you are in the EE bean you looked up it from and fail if not.
last point: in jse provigin a txmgr will be easier
> implement a TransactionManagementService which uses UserTransaction
> -------------------------------------------------------------------
>
> Key: BATCHEE-30
> URL: https://issues.apache.org/jira/browse/BATCHEE-30
> Project: BatchEE
> Issue Type: Improvement
> Components: jbatch-core
> Affects Versions: 0.1-incubating
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 0.2-incubating
>
>
> Some containers do not provide a proper TransactionManager in the specced JNDI location.
> We should try to get a UserTransaction first. And only if this doesn't work we need the JNDI pickup of the native (and always container specific) TransactionManager.
--
This message was sent by Atlassian JIRA
(v6.2#6252)