You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Brian DePradine (JIRA)" <ji...@apache.org> on 2010/03/12 15:04:27 UTC
[jira] Created: (ARIES-248) Add support for precedence when
multiple transaction elements are selected
Add support for precedence when multiple transaction elements are selected
--------------------------------------------------------------------------
Key: ARIES-248
URL: https://issues.apache.org/jira/browse/ARIES-248
Project: Aries
Issue Type: Improvement
Components: Transaction
Reporter: Brian DePradine
Currently, if mutiple transaction elements are defined in blueprint xml then the first matching element is used to determine the transaction strategy to apply. It would be better to define some precedence rules such that the order in which the elements are applied does not matter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ARIES-248) Add support for precedence when
multiple transaction elements are selected
Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian DePradine updated ARIES-248:
----------------------------------
Attachment: patch.txt
Here is a patch that addresses this issues. It applies the following precedence rules:
1) If more that one transaction element matches a particular method name then the elements with the fewest wildcards will be selected, e.g. the pattern 'count*' will be selected in preference to the pattern 'count*Row*' as a match for the method 'countRows'.
2) If more that one transaction element still matches then the elements with the longest patterns will be selected, e.g. the pattern 'countRow*' will be selected in preference to the pattern 'count*'
3) If more than one transaction element still matches then an IllegalStateException is thrown.
> Add support for precedence when multiple transaction elements are selected
> --------------------------------------------------------------------------
>
> Key: ARIES-248
> URL: https://issues.apache.org/jira/browse/ARIES-248
> Project: Aries
> Issue Type: Improvement
> Components: Transaction
> Reporter: Brian DePradine
> Attachments: patch.txt
>
>
> Currently, if mutiple transaction elements are defined in blueprint xml then the first matching element is used to determine the transaction strategy to apply. It would be better to define some precedence rules such that the order in which the elements are applied does not matter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ARIES-248) Add support for precedence when
multiple transaction elements are selected
Posted by "Valentin Mahrwald (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Mahrwald resolved ARIES-248.
-------------------------------------
Resolution: Fixed
Assignee: Timothy Ward
Patch was applied in revision 922285.
> Add support for precedence when multiple transaction elements are selected
> --------------------------------------------------------------------------
>
> Key: ARIES-248
> URL: https://issues.apache.org/jira/browse/ARIES-248
> Project: Aries
> Issue Type: Improvement
> Components: Transaction
> Reporter: Brian DePradine
> Assignee: Timothy Ward
> Attachments: patch.txt
>
>
> Currently, if mutiple transaction elements are defined in blueprint xml then the first matching element is used to determine the transaction strategy to apply. It would be better to define some precedence rules such that the order in which the elements are applied does not matter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.