You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Dominik Przybysz (JIRA)" <ji...@apache.org> on 2017/04/09 18:20:42 UTC

[jira] [Commented] (ARIES-1712) Blueprint maven plugin: common code in transaction factories

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

Dominik Przybysz commented on ARIES-1712:
-----------------------------------------

It was designed in such way to keep pluggable architecture of blueprint maven plugin. Each annotations processors sets should be split to separate jars, which should be independent to each other. It is of course melody of future.

We could extract common code for javax and javax.cdi transaction factories, but spring transaction factory should be kept independent.

> Blueprint maven plugin: common code in transaction factories
> ------------------------------------------------------------
>
>                 Key: ARIES-1712
>                 URL: https://issues.apache.org/jira/browse/ARIES-1712
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>            Reporter: Andrei Shakirin
>
> blueprint maven plugin uses following factories to proceed different kind of transaction annotations: JavaxTransactionFactory, CdiTransactionFactory, CdiTransactionFactory. 
> Basically factories implement very similar functionality triggered by different kind of annotation classes.
> Currently these transacation factories are decoupled one from other, but they repeat a lot of code: namespace handling, attribute writer, etc.
> Proposal: refactor common functionality either to delegate helper or to abstract class. In case if proposal sounds reasonable for you, I will provide the patch.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)