On Jan 8, 2014, at 1:00 PM, Daniel Kulp <[email protected]> wrote:
Haven’t run it yet, but it ends up with:
> 
> WEB-INF/lib/cxf-rt-core-2.7.8.jar
> WEB-INF/lib/cxf-api-2.7.8.jar
> 
> in the war.   There’s likely a conflict with the versions.


Yea.   If you remove the old dependencies, things seem to work fine.

Dan




> 
> Dan
> 
> 
> 
> On Jan 8, 2014, at 12:48 PM, dhogan <[email protected]> wrote:
> 
>> cxf-test-source.jar
>> <http://cxf.547215.n5.nabble.com/file/n5738399/cxf-test-source.jar>  
>> 
>> Hi-
>> Attached in cxf-test-source.jar is a file containing a maven project with
>> the bare-bones classes that reproduce the problem. When I deploy the .war
>> generated by this project to a Tomcat 6.0.36 instance, and hit
>> http://localhost:8080/cxf-test/cxf-test/services, I get the full stack trace
>> below.
>> 
>> I am running on Mac OSX 10.8.5 with a 1.6.0_37 jvm.
>> 
>> Thanks
>> 
>> Dirk
>> 
>> javax.servlet.ServletException: Servlet.init() for servlet publish_test
>> threw exception
>> 
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>>      
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>>      
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
>> 
>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
>>      org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
>>      java.lang.Thread.run(Thread.java:680)
>> root cause
>> 
>> org.apache.cxf.service.factory.ServiceConstructionException
>> 
>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:176)
>> 
>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211)
>>      test.STSBroker.loadBus(STSBroker.java:19)
>> 
>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:76)
>> 
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>>      
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>>      
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
>> 
>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
>>      org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
>>      java.lang.Thread.run(Thread.java:680)
>> root cause
>> 
>> org.apache.cxf.BusException: No DestinationFactory was found for the
>> namespace http://schemas.xmlsoap.org/soap/http.
>> 
>> org.apache.cxf.bus.managers.DestinationFactoryManagerImpl.getDestinationFactory(DestinationFactoryManagerImpl.java:122)
>>      org.apache.cxf.endpoint.ServerImpl.initDestination(ServerImpl.java:88)
>>      org.apache.cxf.endpoint.ServerImpl.<init>(ServerImpl.java:72)
>> 
>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:160)
>> 
>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211)
>>      test.STSBroker.loadBus(STSBroker.java:19)
>> 
>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:76)
>> 
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>>      
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>>      
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
>> 
>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
>>      org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
>>      java.lang.Thread.run(Thread.java:680)
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://cxf.547215.n5.nabble.com/2-7-2-3-0-0milestone1-update-yields-No-DestinationFactory-upon-ws-publish-tp5738355p5738399.html
>> Sent from the cxf-user mailing list archive at Nabble.com.
> 
> -- 
> Daniel Kulp
> [email protected] - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
> 

-- 
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Reply via email to