You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2010/02/09 16:37:27 UTC
[jira] Created: (ARIES-154) Application managed JPA cannot use the
jpa:unit blueprint element without a TransactionSynchronizationRegistry
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
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.
[jira] Work started: (ARIES-154) Application managed JPA cannot use
the jpa:unit blueprint element without a TransactionSynchronizationRegistry
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on ARIES-154 started by Joe Bohn.
> 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.
[jira] Assigned: (ARIES-154) Application managed JPA cannot use the
jpa:unit blueprint element without a TransactionSynchronizationRegistry
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn reassigned ARIES-154:
------------------------------
Assignee: Joe Bohn
> 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.
[jira] Assigned: (ARIES-154) Application managed JPA cannot use the
jpa:unit blueprint element without a TransactionSynchronizationRegistry
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn reassigned ARIES-154:
------------------------------
Assignee: (was: Joe Bohn)
> 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
>
> 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.
[jira] Resolved: (ARIES-154) Application managed JPA cannot use the
jpa:unit blueprint element without a TransactionSynchronizationRegistry
Posted by "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.
[jira] Commented: (ARIES-154) Application managed JPA cannot use
the jpa:unit blueprint element without a TransactionSynchronizationRegistry
Posted by "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.
[jira] Updated: (ARIES-154) Application managed JPA cannot use the
jpa:unit blueprint element without a TransactionSynchronizationRegistry
Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hughes updated ARIES-154:
--------------------------------
Fix Version/s: 0.1
> 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
> Fix For: 0.1
>
>
> 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.
[jira] Assigned: (ARIES-154) Application managed JPA cannot use the
jpa:unit blueprint element without a TransactionSynchronizationRegistry
Posted by "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 reassigned ARIES-154:
----------------------------------
Assignee: Timothy Ward
> 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.