camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schneider <>
Subject Re: No conduit initiator was found for the namespace
Date Thu, 19 Aug 2010 22:52:14 GMT

from what I understand you initialize the service proxy by instatiating 
the service client class. While this may work I would rather configure 
the service proxy in spring and inject the proxy into your bean.
In any case I think the problem is that cxf is not initialized 
correctly. So at least you will have to do some imports. You could try a 
config similar to the wsdl first example from the cxf distribution.
Take a look at the client-applicationContext.xml. I have attached the 
config below.

The sample is not designed for osgi though so I am not sure if 
classloading problems could cause more troubles. Btw. Is there a reason 
you use servicemix for this case? I normally do such implementations as 
wars in a plain tomcat. This environment is much easier to understand.



Am 20.08.2010 00:08, schrieb Roland Villemoes:
> Hi,
> Sounds so nice that this should be easy to fix. I really hope that's true.
> I have attached the source part of the bundle (/src) that contains the
> spring part as well as the webservice proxy etc.
> Thanks a lot.

<beans xmlns=""

<import resource="classpath:META-INF/cxf/cxf.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-http.xml" />

         Define a cxf endpoint based on client stub generated from a 
wsdl. It
         is important to provide serviceName and endpointName so the wsdl is
         not needed at runtime. As far as I know the serviceName and
         endpointName do not have to have a special convention but it is 
         practice to use the service namespace and Service Interface name in
         the names
<jaxws:client id="customerService"

<bean id="tester" 
<property name="customerService" ref="customerService"></property>


View raw message