[ 
https://issues.apache.org/jira/browse/CAMEL-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416658#comment-13416658
 ] 

Luca Foppiano commented on CAMEL-5164:
--------------------------------------

It has been implemented in 2.10.0. This fix made my day! :) 

cool stuff!
                
> Camel error handler stop routing on original route when an exception occur in 
> the splitter using jaxb marshalled objects 
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5164
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5164
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core, camel-jaxb
>    Affects Versions: 2.9.1
>            Reporter: Luca Foppiano
>            Assignee: Claus Ibsen
>             Fix For: 2.9.3, 2.10.0
>
>         Attachments: SplitterAndExceptionRouteTest.java
>
>
> 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 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to