Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <1201306200.151641265729847893.JavaMail.jira@brutus.apache.org>
Date: Tue, 9 Feb 2010 15:37:27 +0000 (UTC)
From: "Valentin Mahrwald (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Created: (ARIES-154) Application managed JPA cannot use the
 jpa:unit blueprint element without a TransactionSynchronizationRegistry
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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.