Re: Aggregator's old Exchange returns null

[Willem Jiang]

Hi,

You can find more explanation in the wiki [1] of AggregationStrategy 
changed in Camel 2.0

http://camel.apache.org/aggregator.html

Willem

Claus Ibsen wrote:
Hi

The oldExchange is null on the first invocation of the aggregation strategy.


On Wed, Jan 20, 2010 at 8:35 PM, lekkie <lekkie.ay...@gmail.com> wrote:
I have a custom aggregator set up. The custom aggregator combines the
exchanges of an old and new one and returns them as one.

However, when I log the old exchange to the ESB log file, it returns null.

See my snippet below

.....

 <route>
       <from uri="direct:RequestProcessor" />
       <to uri="log:Request"/>
       <wireTap uri="direct:ProcessorServices"/>
       <to uri="xslt:requestToManager.xsl"/>
       <convertBodyTo type="javax.xml.transform.dom.DOMSource" />
       <to
uri="nmr:{http://services.locator/}ServicesService:ServicesPort"/>
       <convertBodyTo type="javax.xml.transform.stream.StreamSource" />
       <to uri="direct:ProcessorServices"/>
   </route>

   <route>
       <from uri="direct:ProcessorServices" />
       <to uri="log:Request"/>
       <aggregate strategyRef="myAggregatorStrategy" batchSize="2"
outBatchSize="2">
               <to uri="mock:result"/>
               <to uri="log:Response"/>
           </aggregate>
   </route>

what could b d prob?
--
View this message in context: 
http://old.nabble.com/Aggregator%27s-old-Exchange-returns-null-tp27247326p27247326.html
Sent from the Camel - Users mailing list archive at Nabble.com.