Return-Path: 
 <users-return-6291-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 14008 invoked from network); 4 Apr 2009 03:27:34 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 4 Apr 2009 03:27:34 -0000
Received: (qmail 52607 invoked by uid 500); 4 Apr 2009 03:27:33 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 52529 invoked by uid 500); 4 Apr 2009 03:27:33 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 52519 invoked by uid 99); 4 Apr 2009 03:27:33 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 03:27:33 +0000
X-ASF-Spam-Status: No, hits=4.0 required=10.0
	tests=DNS_FROM_OPENWHOIS,FORGED_YAHOO_RCVD,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 03:27:24 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1LpwX8-0002lq-Js
	for users@camel.apache.org; Fri, 03 Apr 2009 20:27:02 -0700
Message-ID: <22879705.post@talk.nabble.com>
Date: Fri, 3 Apr 2009 20:27:02 -0700 (PDT)
From: ychawla <premiergeneration@yahoo.com>
To: users@camel.apache.org
Subject: Camel CXF Component with ActiveMQ
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: premiergeneration@yahoo.com
X-Virus-Checked: Checked by ClamAV on apache.org


Hello All,
I have a question.  I have a Camel route configured to work with the CXF
component using Camel 1.6.0.  I am trying to invoke a service, send the
message to a queue and send a response.  However, the message seem to hang
in the JMS queue.  Here is the route:

	<cxf:cxfEndpoint id="dropoffSynchronousWebService-endpoint"
		serviceClass="org.wijiscommons.ssaf.drop_off.DropOffSynchronousService"
		address="/DropOffSynchronousService"
		endpointName="s:DropOffSynchronousService"
		serviceName="s:DropOffSynchronousService"
		xmlns:s="http://wijiscommons.org/ssaf/drop-off/"

	/>


	<camelContext xmlns="http://activemq.apache.org/camel/schema/spring">
    
	<route>
		<from uri="cxf:bean:dropoffSynchronousWebService-endpoint?dataFormat=POJO"
/>
		<to uri="bean:ProcessCXFIntoDOMBean?method=process" />
		<to uri="activemq:TEST.FOO"/>
		<to uri="bean:confirmationResponseBean?method=createConfirmationResponse"
/>
	</route>

In activeMQ, I see this error:

Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message was
not received within: 20000 millis on the exchange: Exchange[JmsMessage:
ActiveMQTextMessage

Any ideas?

I also tried to see up the route in a multicast scenario:

		<multicast>
			<pipeline> 
				<to
uri="bean:confirmationResponseBean?method=createConfirmationResponse" />
			</pipeline>	

			<pipeline>
				<convertBodyTo type="java.lang.String"/>
				<to uri="activemq:TEST.FOO"/>
				<to uri="file:C:\temp"/>
			</pipeline>
		</multicast> 

Funny thing with the 2nd example is that the message returned to the client
is the string representation of the input message, rather than the out
message I explicity set in the confirmationResponseBean like this:

exchange.getOut().setBody(returnDoc.getDocumentElement());

If I take activemq out of the equation and have a simple route like this,
all is fine:
	<route>
		<from uri="cxf:bean:dropoffSynchronousWebService-endpoint?dataFormat=POJO"
/>
		<to uri="bean:ProcessCXFIntoDOMBean?method=process" />
		<to uri="bean:confirmationResponseBean?method=createConfirmationResponse"
/>
	</route>


Any ideas?  I have tried all different types of solutions and have had no
luck.

Thanks,
Yogesh
-- 
View this message in context: http://www.nabble.com/Camel-CXF-Component-with-ActiveMQ-tp22879705p22879705.html
Sent from the Camel - Users mailing list archive at Nabble.com.