Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 5 Oct 2011 09:47:34 +0000 (UTC)
From: "Claus Ibsen (Resolved) (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <79454598.11045.1317808054182.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <287688127.3358.1317656313941.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CAMEL-4509) Header not set after dead letter
 queue handles unmarshal error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen resolved CAMEL-4509.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.9.0
                   2.8.2

The work around is either to set the header 2 times, or have a noop operation at first, such as a log, or an empty processor.
                
> 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
>            Assignee: Claus Ibsen
>             Fix For: 2.8.2, 2.9.0
>
>         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