Your workaround works. Thanks. However, I face a new problem now, if I use 2
splitters in the same JBI.
The first one puts the splitSize in a property let's say 'splitSize'.
The second one, represented by the simple following route, uses the same
implementation, so I expect it to overwrite 'splitSize' with the new one:
from(direct:A).splitter(xpath).process(new SplitterProcessor( //puts the
splitSize in 'splitSize' )).
to(direct:B);
But it is not the case. It seems that the previous value is kept. How could
it be explained?
Thanks,
Aymeric
--
View this message in context:
http://www.nabble.com/Trouble-with-camel-splitter-tp21446708s22882p21457564.html
Sent from the Camel - Users mailing list archive at Nabble.com.
