aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1783) TransactionRequiredException when non-transactional method precedes a transactional one in the same service.
Date Mon, 26 Nov 2018 15:23:00 GMT

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

ASF GitHub Bot commented on ARIES-1783:
---------------------------------------

Smasherr opened a new pull request #3: ARIES-1783 EM joins transaction when needed
URL: https://github.com/apache/aries-jpa/pull/3
 
 
   EMSupplier makes a cached EM join a transaction if there is currently
   an active one.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>            Priority: Major
>
> 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)

Mime
View raw message