Hi

Yeah I dont see a problem either. Multicast can be 1 or N destinations.

Maybe you can try explain again what you see as a problem? and what
you want to do be able to do instead.

Are you wanting to do a multicast to zero destinations which doesnt make sense?


On Wed, Oct 2, 2013 at 7:44 AM, kraythe . <kray...@gmail.com> wrote:
> It would work. Multicast doesnt indicate anything more than more than one
> destination. Those destinations could be two JMS queues, a queue and a log,
> whatever you like. All your code would do is log the message but if that is
> what you want then go for it.
>
> *Robert Simmons Jr. MSc. - Lead Java Architect @ EA*
> *Author of: Hardcore Java (2003) and Maintainable Java (2012)*
> *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39*
>
>
> On Tue, Oct 1, 2013 at 4:34 PM, Christian Müller <
> christian.muel...@gmail.com> wrote:
>
>> This doesn't sounds right.
>> Can you provide a unit test which shows this behavior and attach it to a
>> JIRA [1]!?
>>
>> [1] http://camel.apache.org/contributing.html
>>
>> Best,
>> Christian
>> -----------------
>>
>> Software Integration Specialist
>>
>> Apache Camel committer: https://camel.apache.org/team
>> V.P. Apache Camel: https://www.apache.org/foundation/
>> Apache Member: https://www.apache.org/foundation/members.html
>>
>> https://www.linkedin.com/pub/christian-mueller/11/551/642
>>
>>
>> On Tue, Oct 1, 2013 at 12:28 PM, arunodhaya80 <t...@arunma.com> wrote:
>>
>> > Please excuse stupidity as this is my first Camel application
>> >
>> > 1. To respond to a web request, I am sourcing the content from two
>> > different
>> > sources.
>> > 2. I am, therefore, making a multicast request to two methods and
>> > parallelizing it.
>> > 3. The response is an marshalled JSON object (using camel-jackson)
>> >
>> > All works fine.
>> >
>> >     public class RestToBeanRouter extends RouteBuilder{
>> >
>> >     @Override
>> >     public void configure() throws Exception {
>> >
>> >         from("cxfrs://bean://rsServer")
>> >
>> >                 .multicast()
>> >                 .parallelProcessing()
>> >                 .aggregationStrategy(new CoreSearchResponseAggregator())
>> >                 .beanRef("searchRestServiceImpl", "firstMethod")
>> >                 .beanRef("searchRestServiceImpl", "secondMethod")
>> >                 .end()
>> >                 .marshal().json(JsonLibrary.Jackson)
>> >                 .to("log://camelLogger?level=DEBUG");
>> >
>> >     }
>> >
>> >
>> > **Question :**
>> >
>> > The Multicast routing expects a `to` in the DSL.  Currently, I am mapping
>> > this to a `log` endpoint.  Is this fine?
>> >
>> > Since I am not using the `to` and the last exchange of the Aggregator
>> > strategy is the one which is returned to the user, should my endpoint be
>> > configured to something else - like a null or something? (Ah, the
>> stupidity
>> > kicks in)
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> >
>> http://camel.465427.n5.nabble.com/Apache-Camel-Multicast-Is-there-a-null-or-a-similar-endpoint-tp5740664.html
>> > Sent from the Camel - Users mailing list archive at Nabble.com.
>> >
>>



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Reply via email to