Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <9749239.1202506777197.JavaMail.jira@brutus>
Date: Fri, 8 Feb 2008 13:39:37 -0800 (PST)
From: "Hadrian Zbarcea (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-291) MulticastRecipientList - recipient
 list that uses multicast processor
In-Reply-To: <1656500.1200408404984.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Hadrian Zbarcea resolved CAMEL-291.
-----------------------------------

    Resolution: Fixed

Przemyslav,

I decided to not apply the patch and fix the RecipientList instead.  The change is similar to your patch with the only notable change that I used multicast with a UseLatestAggregationStrategy to preserve the previous semantics.  That is it works as expected for in only and as before for in/out(s) - last result is returned.  Currently the strategy is hardcoded and I don't see a serious reason to make it pluggable as one could use multicast for that.  If you disagree please reopen the issue and comment.

That said, you get credit both for spotting this and for the patch.  Thanks and keep them coming!

> MulticastRecipientList - recipient list that uses multicast processor
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-291
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-291
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Przemyslaw Budzik
>            Assignee: Hadrian Zbarcea
>             Fix For: 1.3.0
>
>         Attachments: multicast-recipient-list.patch
>
>
> Probably it would be useful to have recipientList that in InOut mode doesn't work as a pipeline. I faced that problem, however InOnly is ok. It seems 
> in InOut it reminds of RoutingSlip. Optionally we could use MulticastProcessor to process "recipients". If you think it makes sense, attached patch enhances camel-core with such feature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.