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

[jira] [Issue Comment Deleted] (ARIES-1708) Incorrect processing of duplicated patterns

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

Andrei Shakirin updated ARIES-1708:
-----------------------------------
    Comment: was deleted

(was: Patch)

> Incorrect processing of duplicated patterns
> -------------------------------------------
>
>                 Key: ARIES-1708
>                 URL: https://issues.apache.org/jira/browse/ARIES-1708
>             Project: Aries
>          Issue Type: Bug
>          Components: Transaction
>    Affects Versions: transaction-blueprint-1.1.1
>            Reporter: Andrei Shakirin
>
> In case if transaction pattern is used more than once for the same component, the transaction-blueprint module throws following exception:
> {code}
> Unable to apply patterns {.*, .*}.
> {code}
> It caused by following: map in TxComponentMetaDataHelperImpl.TranData uses Pattern as a key. Pattern class doesn't implement equals() method and duplicated patterns can be saved in the map. 
> That causes exception on later processing steps, because code cannot find fewest and longest pattern.
> Proposal:
> a) use wildcard string instead Pattern object as map key
> b) in case if more than one pattern stays after selection, just use the first one instead exception.
> This case happens often by using blueprint maven plugin generating transaction attribute in xml configuration and enabling annotations scan for the same beans.
> Patch is attached



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