Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <17236111.post@talk.nabble.com>
Date: Wed, 14 May 2008 10:03:33 -0700 (PDT)
From: runr <russ_evans@freddiemac.com>
To: camel-user@activemq.apache.org
Subject: Re: Missing Headers in pipline with bean components
In-Reply-To: <17234481.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <17234481.post@talk.nabble.com>


vmasina wrote:
> 
> Is it by design Headers will not be propagated to next component in the
> route, after the bean component in the route?
> 

I had a similar issue and was advised that Headers tend to be specific to
the endpoint technology and are lost when changing to a different endpoint
technology.  Instead, you should use an Exchange property to hold your
application-specific information.  The property will be maintained until it
is explicitly removed.

I think you want something like this:

//SET PROPERTY BEFORE PROCESSING THE THIRD PARTY REQUEST 
from("activemq:queue:provider2Transformer") 
.process(new Processor(){ 
        public void process(Exchange arg0) throws Exception { 
		arg0.setProperty( "STUDENT_ID", studentId );
        } 

//UPDATE STATUS AFTER PROCESSING THE THIRD PARTY REQUEST 
from("activemq:queue:updateThirdPartyProvisioningStatus") 
.process(new Processor(){ 
        public void process(Exchange arg0) throws Exception { 
                System.out.println( arg0.getProperty("STUDENT_ID")); 
        } 


Russ
-- 
View this message in context: http://www.nabble.com/Missing-Headers-in-pipline-with-bean-components-tp17234481s22882p17236111.html
Sent from the Camel - Users mailing list archive at Nabble.com.