[jira] Commented: (ARIES-154) Application managed JPA cannot use the jpa:unit blueprint element without a TransactionSynchronizationRegistry

["Joe Bohn (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARIES-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834301#action_12834301 ] 

Joe Bohn commented on ARIES-154:
--------------------------------

I made the service optional but I haven't had a chance yet to find the right places to issue messages when the service is really necessary but not available.   I'll unassign it so that somebody else can pick it up if they get to it before I do.


> Application managed JPA cannot use the jpa:unit blueprint element without a TransactionSynchronizationRegistry
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-154
>                 URL: https://issues.apache.org/jira/browse/ARIES-154
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA
>            Reporter: Valentin Mahrwald
>            Assignee: Joe Bohn
>
> Currently, the jpa-container-context bundle has a mandatory service dependency on TransactionSynchronizationRegistry. This both unnecessary and potentially crippling (if the framework does not have one).
> Instead the service dependency should probably be optional and the jpa-container-context should log a warning when it is started without a TranSyncRegistry and an error when a jpa:context element is used without one.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.