Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <15209038.1200661822009.JavaMail.jira@brutus>
Date: Fri, 18 Jan 2008 05:10:22 -0800 (PST)
From: "Przemyslaw Budzik (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Updated: (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 ]

Przemyslaw Budzik updated CAMEL-291:
------------------------------------

    Attachment:     (was: multicast-recipient-list.patch)

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