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

["Timothy Ward (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARIES-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Ward resolved ARIES-154.
--------------------------------

    Resolution: Fixed

The container.context bundle now issues warnings when the TransactionSynchronizationRegistry changes or disappears, or if a blueprint references a managed persistence context and no TransactionSynchronizationRegistry is available.

It also provides an info message when the TransactionSynchronizationRegistry is added for the first time/after being removed, and a debug message if a managed persistence context is used when no TransactionSynchronizationRegistry is available.

> 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: Timothy Ward
>
> 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.