You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Daniel Estermann (JIRA)" <ji...@apache.org> on 2018/02/20 10:58:00 UTC

[jira] [Created] (ARIES-1783) TransactionRequiredException when non-transactional method precedes a transactional one in the same service.

Daniel Estermann created ARIES-1783:
---------------------------------------

             Summary: TransactionRequiredException when non-transactional method precedes a transactional one in the same service.
                 Key: ARIES-1783
                 URL: https://issues.apache.org/jira/browse/ARIES-1783
             Project: Aries
          Issue Type: Bug
          Components: JPA
    Affects Versions: jpa-2.5.0
            Reporter: Daniel Estermann


Assume I have a service implementation with a method annotated with @Transactional and one of TxTypes not starting a transaction:
 * NEVER
 * NOT_SUPPORTED
 * SUPPORTS

From that non-transactional method I want to use a self-reference resolved via BundleContext to call a transactional method in the same service, annotated with one of those TxTypes:
 * REQUIRED
 * REQURES_NEW

Since the resolved self-reference is a proxied object I expect it to be able to start a new transaction. This is not the case however and the subject exception occurs.

 

I created a test case revealing the issue in the following pull request: https://github.com/apache/aries-jpa/pull/2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)