SplitterPage comment added by Jeremy LucierA small suggestion on stopOnException. I'd add that by default the message that's contained in the exchange after an error terminates the split operation, is the message that was split out and not the message that began the splitter operation. This took me way too many hours to figure out that the stopOnException was the reason my error handling wasn't doing the correct thing.
Change Notification Preferences
View Online
|
|
- [CONF] Apache Camel > Splitter confluence
- [CONF] Apache Camel > Splitter confluence
- [CONF] Apache Camel > Splitter Claus Ibsen (Confluence)
- [CONF] Apache Camel > Splitter Claus Ibsen (Confluence)
