Dear all, I've been digging into this problem for some time now and I haven't find why this is happening. I'm using camel 2.9.1. The whole problems is quite complicated to explain, I've created a test that reproduce the error that might be more useful.
I have a route that get some XML and transform it with a processor in an object generated from XSD with JAXB. After that the object (transported as XML) is then split based a certain logic. The route uses the deadLetterCHannel error handler to a 'reject' endpoint. Now, sometimes when I get some invalid character in the input file (0x10 eg.) (in my processor I don't polish them), the splitter will crash but, instead of detouring only the messages that contains errors to the deadLetterChanne, it will detour every message coming after the error occurs. I know that I can fix the problem in the processor by removing the invalid characters, but in my opinion, camel should be more robust and doesn't block the entire processing for a "non fatal" error. Or I should use a different way for doing what I'm doing... Please have a look at the code and let me know, I think is a bug but I'm waiting for your opinion. Thanks in advance -- Luca Foppiano Software Engineer +31615253280 l...@foppiano.org www.foppiano.org
