Hi Ryan,
Your exception shows that inside servicemix the cxf-se can't load
cxf-http transport, this behavior is intended since inside servicemix
we should use cxf-jbi transport.
Your code can run successfully outside servicemix doesn't mean it can
run successfully inside servicemix, the configuration is not same.The
cxf-se shouldn't use any jetty jar IIRC.
Basicly, when we create client inside cxf-se, something should be like
JaxWsProxyFactoryBean cf = new JaxWsProxyFactoryBean();
cf.setServiceName(getService());
cf.setServiceClass(type);
cf.setAddress("jbi://" + new
IdGenerator().generateSanitizedId());// to use cxf-jbi transport
cf.setBindingId(org.apache.cxf.binding.jbi.JBIConstants.NS_JBI_BINDING);//
to use cxf-jbi binding
return cf.create();
But We already support client proxy now in cxf-se, from which we set
all for you and you needn't worry the details. You can get more
details how the client-proxy is working form [1] [2]
[1]http://svn.apache.org/repos/asf/incubator/servicemix/trunk/deployables/serviceengines/servicemix-cxf-se/src/test/java/org/apache/servicemix/cxfse/CxfSeClientProxyTest.java
[2]
http://svn.apache.org/repos/asf/incubator/servicemix/trunk/deployables/serviceengines/servicemix-cxf-se/src/test/resources/org/apache/servicemix/cxfse/client-proxy.xml
Would you please try the client-proxy in cxf-se, I believe it's the
better way for you.
Best Regards
Freeman
On 10/2/07, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> sorry, I meant for a 3rd party webservice... my fingers have a mind of their
> own.
>
> On 10/1/07, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> >
> > I'm trying to figure out if I'm going about this the wrong way (which I'm
> > sure I am)... I have a cxfse service that I'm using as an abstraction to
> > several third party related services. To do this, I generated a CXF
> client
> > for a 3rd party service and attempt to invoke it from my service. The
> > problem is, I get this error:
> >
> > org.apache.cxf.phase.PhaseInterceptorChain doIntercept
> > INFO: Interceptor has thrown exception, unwinding *now*
> > org.apache.cxf.interceptor.Fault: *No* *conduit* *initiator* *was* *found*
> > * for* *the*
> > *namepsace* http://schemas.xmlsoap.org/soap/http.
> > at
> >
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:85)
> >
> > at
> > org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:82)
> >
> > at
> >
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:56)
> >
> > at
> > org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(
> > ServiceInvokerInterceptor.java:56)
> > at
> > org.apache.cxf.workqueue.SynchronousExecutor.execute(
> > SynchronousExecutor.java:37)
> > at
> > org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(
> > ServiceInvokerInterceptor.java:87)
> > at
> > org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
> > PhaseInterceptorChain.java:206)
> >
> > Now, I know what the solution is to it, but the problem is.. I already
> > have my client configured correctly. When I invoke my client (it's a
> maven
> > 2 project) outside of servicemix it's fine, but when I have my service
> > bundle it and try to use it, I get that error. I did notice that the
> cxfse
> > component is missing some of the jetty jars which I initially thought
> might
> > be the problem. I included them but I still have the error. Is there a
> > better way if I have a cxf client I generated to use it inside of my
> > service?
> >
>
