Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <708371711.38041270629693756.JavaMail.jira@brutus.apache.org>
Date: Wed, 7 Apr 2010 08:41:33 +0000 (UTC)
From: "Valentin Mahrwald (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Resolved: (ARIES-248) Add support for precedence when
 multiple transaction elements are selected
In-Reply-To: <979959708.227051268402667128.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.