deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DELTASPIKE-310) Support for TransactionAttributeType REQUIRE_NEW
Date Fri, 18 Jan 2013 17:18:13 GMT

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

Gerhard Petracek resolved DELTASPIKE-310.
-----------------------------------------

    Resolution: Won't Fix

there isn't a portable way to do it for 'RESOURCE_LOCAL' transactions
                
> Support for TransactionAttributeType REQUIRE_NEW 
> -------------------------------------------------
>
>                 Key: DELTASPIKE-310
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-310
>             Project: DeltaSpike
>          Issue Type: Improvement
>          Components: JPA-Module
>    Affects Versions: 0.4-incubating
>            Reporter: Alexis Krier
>             Fix For: 0.5-incubating
>
>
> @Transactional currently open a transaction when method is invoked.
> if a sub method is invoked also annoted @Transactional the second method uses the first
method transaction and not a new one.
> ex:
> @Transactional
> void createEntity(){
>   ...
>   audit()
>    throw Exception("a problem occurs here")
> }
> @transactional
> void audit(){
>    //persist some audit stuff
>    ...
> }
> Actually everything is rolled back because of the exception in the top method (createEntity)
> @transactional should have a parameter like (REQUIRE_NEW, NEVER...) to handle with details
transaction's lifecycle

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message