Hi, I tried with servicemix-saxon SE. Now, I can see in the log file that the correlation ID is sent to the aggregator component. But I got still the same error : http://www.nabble.com/file/5559/servicemix.log servicemix.log > incoming exchange"
-> I put the servicemix log file in attachement Thanks for your help Sebastien gnodet wrote: > > Have you tried with servicemix-saxon SE instead of the > lightweight component ? > > On 1/9/07, sebastien <[EMAIL PROTECTED]> wrote: >> >> hi all, >> >> I use the followings components : >> >> -> XSLT (x) -> HTTP >> (pipeline) >> HTTP -> Splitter -> Recipient List >> -> Aggregator -> JMS >> -> XSLT (x) -> HTTP >> (pipeline) >> >> I can see in the log file that XSLT component does not send the >> correlation >> ID property. >> It causes the following error in the Aggregator component : >> "java.lang.IllegalArgumentException: Could not retrieve correlation id >> for >> incoming exchange" >> >> Have you got an idea ? >> >> Tanks for your help. >> >> Sebastien >> >> I tried with ServiceMix 3.0 and ServiceMix 3.1 version without any >> success. >> -- >> View this message in context: >> http://www.nabble.com/Correlation-ID-lost-after-XSLT-component-tf2945039s12049.html#a8235443 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/Correlation-ID-lost-after-XSLT-component-tf2945039s12049.html#a8253993 Sent from the ServiceMix - User mailing list archive at Nabble.com.
