camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wayne Keenan <>
Subject Re: Virtual/Proxy WebService component (request?) R
Date Fri, 12 Mar 2010 14:16:18 GMT

I tried the jetty/http combo but dont like the fact the WSDL service URL to
the SCA component 'leaked' straight thru verbatim.

The real client will be a b2b gateway that wont consume the WSDL directly,
so not a problem.  But for dev/testing I would like SOAPui to use the Camel
fronted endpoint and not be given the backend endpoint serivce URL.

The Synapse proxy rewrites the service endpoint.


On Fri, Mar 12, 2010 at 1:01 PM, Willem Jiang <>wrote:

> Hi,
> Does you client need to use the service WSDL to generate the question
> message?
> If so, I'm afraid you still need to let camel-cxf know about the WSDL or
> generate the artifact with WSDL.
> Otherwise, you can leverage the camel-jetty and camel-http component to
> route the request to backend system.
> Willem
> Wayne Keenan wrote:
>> Hi,
>> I have backend SCA components that is implemented in Java and the WSDL is
>> automatically generated by the Apache Tuscany SCA container.
>> I would like to be able to front access to my backend services using
>> Camel.
>> For this to function I would like to know it its possible to configure a
>> (the CXF?) component to advertise the SCA generated WSDL (modifying the
>> endpoint ports so not to expose the backed endpoint directly) and route
>> thru
>> Camel to the backend service.  Thus, I could redirect/loadbalance or what
>> ever without effecgting the client,
>> Basically I want todo what Apache Synapse can do, but in Camel:
>> It would be good if the component could do WSDL loading lazyly to account
>> for situations whereby the SCA service has not started when the Camel
>> route
>> is started. (Like I have now :) )
>> All the best,
>> Wayne

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message