Return-Path: 
 <users-return-6243-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 8117 invoked from network); 31 Mar 2009 19:48:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 31 Mar 2009 19:48:11 -0000
Received: (qmail 89350 invoked by uid 500); 31 Mar 2009 19:48:10 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 89303 invoked by uid 500); 31 Mar 2009 19:48:10 -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 89293 invoked by uid 99); 31 Mar 2009 19:48:10 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Mar 2009 19:48:10 +0000
X-ASF-Spam-Status: No, hits=4.1 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WEIRD_PORT,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.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; Tue, 31 Mar 2009 19:48:01 +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 1Lojvw-0003Vt-Sw
	for users@camel.apache.org; Tue, 31 Mar 2009 12:47:40 -0700
Message-ID: <22809337.post@talk.nabble.com>
Date: Tue, 31 Mar 2009 12:47:40 -0700 (PDT)
From: notsure <l.hillery@gmail.com>
To: users@camel.apache.org
Subject: Re: Camel Transport for CXF
In-Reply-To: <49D241EE.6030100@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: l.hillery@gmail.com
References: <22787141.post@talk.nabble.com> <49D1EE73.6010802@gmail.com>
 <22802542.post@talk.nabble.com> <49D241EE.6030100@gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org


Thanks for the validation, I did switch to the jetty component after reading
the documentation a few times. However I can no longer access my wsdl file,
how do I fix that?



willem.jiang wrote:
> 
> No, you should not use the Camel transport for CXF for your case
> Basically, if you want to leverage the Camel's component to implement a
> new transport for CXF  , you can use this Camel Transport for CXF.
> 
> But for your case, you just need to route the SOAP request to different
> service endpoints. You can use the jetty endpoint to listen for soap
> request, and then route the request to different base on the namespace.
> 
> from(jetty://YourServiceAddress).choice(xxx)...
> 
> Willem
> 
> notsure wrote:
>> Thank you for the timely response, I have the camel-cxf.jar in the
>> classpath.
>> I'm trying to set my routes and I get a looping issue. I would like to
>> achieve the 
>> following:
>> 
>> Service A receives a soap message and routes it to an outside service
>> based
>> on content
>> of the soap (namespace most likely) it could go to several ports 
>> B (namespace B) 
>> C (namespace C)
>> D (namespace D)
>> E (namespace E)
>> 
>> and the response is routed back to the service and forwarded to the
>> original
>> requestor.
>> I'm currently using Camel Transport for CXF and route looks like
>> <camel:destination
>> 		name="{http://service.acme.train.com}ServiceSoapPort.http-destination">
>> 		<camelContext id="context"
>> xmlns="http://camel.apache.org/schema/spring">
>> 			<route>
>> 				<from uri="direct:ServiceSoapPort" />
>> 				<pipeline>
>> 					<choice>
>> 						<when>
>> 							<xpath>$axe='uri:AXE/ACTION=SOAPACTIONwsdl'
>> 							</xpath>
>> 							<inOut uri="http://localhost:9010/ACTION=SOAPACTION" />
>> 						</when>
>> 						<when>
>> 							<xpath>$cl =
>> 								'uri:CLASSSERVER/ACTION=SOAPACTIONwsdl'</xpath>
>> 							<inOut uri="http://localhost:9020/ACTION=SOAPACTION" />
>> 						</when>
>> 						<when>
>> 							<xpath>$ua = 'uri:UASERVER/ACTION=SOAPACTIONwsdl'</xpath>
>> 							<inOut uri="http://localhost:9030/ACTION=SOAPACTION" />
>> 						</when>
>> 						<when>
>> 							<xpath>$vw = 'uri:VIEW/ACTION=SOAPACTIONwsdl'</xpath>
>> 							<inOut uri="http://localhost:9080/ACTION=SOAPACTION" />
>> 						</when>
>> 						<otherwise>
>> 							<inOut uri="http://localhost:9000/ACTION=SOAPACTION" />
>> 						</otherwise>
>> 					</choice>
>> 				</pipeline>
>> 			</route>
>> 		</camelContext>
>> 	</camel:destination>
>> 
>> 
>> 
>> willem.jiang wrote:
>>> Hi,
>>>
>>> Did you put the camel-cxf.jar into your class path?
>>> BTW, Since we use the Spring customer namespace handler to deal with the
>>> camel:destination please make sure the camel-cxf.jar's
>>> META-INF/spring.handlers and META-INF/spring.schemas are loadable by
>>> Spring.
>>>
>>> Willem
>>>
>>> notsure wrote:
>>>> I have a jaxws endpoint which im trying to generate an http endpoint to
>>>> transport soap messages to a secondary service(request/response). I'm
>>>> using
>>>> eclipse 3.4.2, cxf 2.1.4 and camel 2.0 m1. The secondary service has
>>>> five
>>>> endpoints so I've been trying to use pipeline with filter using xpath.
>>>> However, when I add camel:destination to my applicationcontext
>>>> eclipse/tomcat cannot find it. 
>>>>
>>>> snippets
>>>>
>>>> xmlns:camel="http://cxf.apache.org/transports/camel"
>>>>
>>>> http://cxf.apache.org/transports/camel
>>>>     http://cxf.apache.org/transports/camel/camel.xsd"
>>>>
>>>> <camel:destination
>>>> 		name="{http://localhost:8080}ServiceSoapPort.http-destination">
>>>> 		<camelContext id="context"
>>>> xmlns="http://camel.apache.org/schema/spring/">
>>>> 			<route>
>>>>
>>> Any feedback would be greatly appreaciated.
>>>
>>> Thanks,
>>> Terry
>>>
>>>> I know the url doesn't resolve and I've copied the xsd from the jar
>>>> file,
>>>> what can i do to resolve this?
>>>>
>>>
>>>
>> 
> 
> 
> 
:-D:-D
-- 
View this message in context: http://www.nabble.com/Camel-Transport-for-CXF-tp22787141p22809337.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.