Hi
Ah so the JBI2 loses these headers?
I guess they are not propogated as they are kinda internal since they
are prefixed with org.apache.camel
As a workaround you can use a processor or the likes to copy these
headers into your own header name so they wont be filtered.
rom(JBI1).splitter(xpath).process(new Processor() ....
// java code here where you copy to your own headers
);to(JBI2);
On Wed, Jan 14, 2009 at 11:38 AM, avermout <averm...@gmail.com> wrote:
>
> Hello,
>
> Thanks for your help.
> Th bodyType is DOMSource, and neither splitSize or splitCounter are
> propagated to my target. What is looking strange is that I don't see any
> splitSize in the traces generated by the TraceFormatter, but well in the
> logs from the instrumentationProcessor. For example,
> Recording duration: 66.817641 millis for exchange: Exchange[JbiMessage:
> org.apache.servicemix.jbi.messaging.normalizedmessagei...@770494{properties:
> {org.apache.camel.splitSize=2, ....., org.apache.camel.splitCounter=0}}
>
> My message seems to be splitted in the right way, but splitSize is not well
> propagated.
>
> Thanks,
> Aymeric
>
>
> Claus Ibsen-2 wrote:
>>
>> - Can you see the other header that is added: splitCounter?
>> - What is the body type?, because Camel invokes size() on the type
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Trouble-with-camel-splitter-tp21446708s22882p21453485.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
