On Tue, Apr 5, 2011 at 1:03 PM, Mond Raymond <mondraym...@gmail.com> wrote:
> I want to get data from three sources:
>
>       from(fromURI).multicast().to("seda:coreVehicleData",
> "seda:warrantyVehicleData", "seda:accessoryVehicleData");
>
>
> from("seda:coreVehicleData").to("bean:coreVehicleData").to("seda:vehicleDataAggregator");
>
> from("seda:warrantyVehicleData").to("bean:warrantyVehicleData").to("seda:vehicleDataAggregator");
>
> from("seda:accessoryVehicleData").to("bean:accessoryVehicleData").to("seda:vehicleDataAggregator");
>
>        from("seda:vehicleDataAggregator")
>                .aggregate(header(aggregateHeaderName), new
> VehicleDataAggregator())
>                .completionSize(correctNumberOfResponses)
>                .aggregationRepository(combinedVehicles)
>                .completionTimeout(timeoutInMilliseconds)
>                .eagerCheckCompletion()
>                .to(toUri);
>
> This all works very nicely in the 'happy case'.  I have a client that looks
> like this:
>
>    public CombinedVehicleData getCombinedVehicleData(Vin vin) {
>        producer.sendBodyAndHeader(toUri, vin, aggregateHeaderName, vin);
>        return consumer.receiveBody(fromUri, CombinedVehicleData.class);
>    }
>
> Again it all works nicely in the happy case.
>
> If I force a timeout in one of the SEDA components however I do not see an
> exception - I don't count the nullpointer when I reference the response ;-)
>
> Do I have to add a special errorhandler clause to influence this behaviour?
>

You need to handle the exception in your aggregation strategy. The
Camel book (chapter 8) shows your options for that.
I dont recall if we got any wiki documentation for that. Contributions
is welcome


> Thanks
>
> Ray
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/aggregator-error-handling-default-does-not-propogate-error-tp4283684p4283684.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Reply via email to