aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Ward (Commented) (JIRA)" <>
Subject [jira] [Commented] (ARIES-628) Support JTA attributes by annotations
Date Mon, 06 Feb 2012 11:11:59 GMT


Timothy Ward commented on ARIES-628:

I have added basic support, using a simple annotation in the new org.apache.aries.transaction.annotations
package. What do people think of this approach? It can be altered/enhanced to understand the
javax.ejb and org.springframework equivalents.

I see another major improvement as being the ability to distinguish methods based on parameters
as well as name (to allow overloaded methods to have different transaction semantics). Does
anyone else have any suggestions in this area?
> Support JTA attributes by annotations
> -------------------------------------
>                 Key: ARIES-628
>                 URL:
>             Project: Aries
>          Issue Type: New Feature
>          Components: Transaction
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Timothy Ward
> currently, we can use a Blueprint descriptor to define the transaction attribute associated
to methods:
> <bean id="myPojo" class="myPojo" init-method="init">
>   <tx:transaction method="set*" value="Required"/>
>   <tx:transaction method="get*" value="Supported"/>
> </bean>
> I think it could be interesting for the users to define transaction attributes directly
in the POJO using annotations.
> For instance, it could be helpful to support the following annotations:
> @PostConstruct
> @PreDestroy
> @Resource
> @TransactionAttribute
> For instance, myPojo will look like:
> public class MyPojo {
>   @TransactionAttribute=Required
>   public void setData(Data data) {
>     ...
>   }
> } 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message