Hi, Could you check if cxf-rt-bindings-soap jar is in WEB-INF/lib of.war file as well?
Regards, Andrei. > -----Original Message----- > From: dhogan [mailto:[email protected]] > Sent: Dienstag, 7. Januar 2014 23:28 > To: [email protected] > Subject: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon > ws-publish? > > I am upgrading my cxf/sts/wss4j dependencies, and am running into the > following error when publishing a web-service in the initialization of my > CXFNonSpringServlet. This code worked fine on the 2.7.2 code-base, but is > throwing the following exception on the 3.0.0-milestone1 versions. > > org.apache.cxf.BusException: No DestinationFactory was found for the > namespace http://schemas.xmlsoap.org/soap/http. > > org.apache.cxf.bus.managers.DestinationFactoryManagerImpl.getDestinatio > nFactory(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(JaxWsServerFactoryB > ean.java:211) > org.forgerock.openam.sts.STSBroker.loadBus(STSBroker.java:45) > > Here is the code which generates the error: > public class STSBroker extends CXFNonSpringServlet { > @Override > public void loadBus(ServletConfig servletConfig) { > super.loadBus(servletConfig); > Bus bus = getBus(); > BusFactory.setDefaultBus(bus); > JaxWsServerFactoryBean serverFactoryBean = new > JaxWsServerFactoryBean(); > serverFactoryBean.setAddress("/sts_publish/"); > serverFactoryBean.setServiceBean(new STSPublishImpl()); > serverFactoryBean.create(); //this is line 45 in the stack-trace above > } > } > > The listing of updated dependencies follow. No code changes were made > other than the import statement changes required by the migration from > org.apache.ws.security to org.apache.wss4j in the STS (and these seem > unrelated to the error). I confirmed the presence of cxf-rt-transports-http > and cxf-rt-transports-http-jetty .jar files in WEB-INF/lib of my .war file, as > that seemed to be a culprit in previous manifestations of the soap “No > DestinationFactory was found” error. > > Maven version changes: > cxf-rt-frontend-jaxws: 2.7.2->3.0.0-milestone1 > cxf-rt-transports-http:2.7.2->3.0.0-milestone1 > cxf-rt-core:2.7.2->2.7.8 > cxf-rt-bindings-soap:2.7.2->3.0.0-milestone1 > cxf-api:2.7.2->2.7.8 > cxf-rt-transports-http-jetty:2.7.2->3.0.0-milestone1 > cxf-rt-ws-security:2.7.2->3.0.0-milestone1 > cxf-rt-ws-policy:2.7.2->3.0.0-milestone1 > cxf-services-sts-core:2.7.2->3.0.0-milestone1 > wss4j(org.apache.ws.security):1.6.9->1.6.13 > xmlsec(org.apache.santuario):1.5.3->1.5.6 > > Any ideas? > > Thanks > > Dirk > > > > > -- > View this message in context: http://cxf.547215.n5.nabble.com/2-7-2-3-0- > 0milestone1-update-yields-No-DestinationFactory-upon-ws-publish- > tp5738355.html > Sent from the cxf-user mailing list archive at Nabble.com.
