[ 
https://issues.apache.org/jira/browse/CAMEL-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roy Truelove updated CAMEL-4509:
--------------------------------

    Description: 
We have a route which unmarshals a soap msg into an object.  On that route is a 
dead letter queue error handler.  That DLQ sets headers on the message used 
later for error reporting.

If the error is thrown by the marshaller, the *first header* that we try to set 
is wiped out.  The 2nd header is set with no problem.  If an error is thrown by 
something other than the marshaller, the correct headers are set.

See attached project with failed test case (canSetHeadersOnBadXmlDeadLetter)

  was:
We have a route which unmarshals a soap msg into an object.  On that route is a 
dead letter queue error handler.  That DLQ sets headers on the message used 
later for error reporting.

If the error is thrown by the marshaller, the *first header* that we try to set 
is wiped out.  The 2nd header is set with no problem.

See attached project with failed test case (canSetHeadersOnBadXmlDeadLetter)

    
> Header not set after dead letter queue handles unmarshal error
> --------------------------------------------------------------
>
>                 Key: CAMEL-4509
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4509
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.8.1
>         Environment: Java version: 1.6.0_11, vendor: Sun Microsystems Inc.
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
>            Reporter: Roy Truelove
>         Attachments: marshalBug.zip
>
>
> We have a route which unmarshals a soap msg into an object.  On that route is 
> a dead letter queue error handler.  That DLQ sets headers on the message used 
> later for error reporting.
> If the error is thrown by the marshaller, the *first header* that we try to 
> set is wiped out.  The 2nd header is set with no problem.  If an error is 
> thrown by something other than the marshaller, the correct headers are set.
> See attached project with failed test case (canSetHeadersOnBadXmlDeadLetter)

--
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