You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by dhogan <di...@forgerock.com> on 2014/01/07 23:27:46 UTC

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.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)
	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.

Re: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon ws-publish?

Posted by Daniel Kulp <dk...@apache.org>.
On Jan 8, 2014, at 1:57 PM, dhogan <di...@forgerock.com> wrote:

> Thanks for the resolution. What are the old dependencies? Is there a good
> place I can look to know the correct dependency set for various version? I
> found http://cxf.apache.org/docs/cxf-dependency-graphs.html, but it does not
> seem to tell me what I need to know.

Mostly the cxf-rt-core and cxf-api.   Both don’t exist in 3.0.0 as they were combined into a single cxf-core.   Just remove those and you should be “OK” as cxf-core will be pulled in transitively from the other CXF dependencies.

I think you would need to remove the WSS4J 1.6 dep as well as 3.0 would require the 2.0-beta.  Again, that can be pulled in transitively from cxf-rt-ws-security.

Dan


> 
> 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-tp5738355p5738402.html
> Sent from the cxf-user mailing list archive at Nabble.com.

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon ws-publish?

Posted by dhogan <di...@forgerock.com>.
Thanks for the resolution. What are the old dependencies? Is there a good
place I can look to know the correct dependency set for various version? I
found http://cxf.apache.org/docs/cxf-dependency-graphs.html, but it does not
seem to tell me what I need to know.

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-tp5738355p5738402.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon ws-publish?

Posted by Daniel Kulp <dk...@apache.org>.
On Jan 8, 2014, at 1:00 PM, Daniel Kulp <dk...@apache.org> 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 <di...@forgerock.com> 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
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
> 

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon ws-publish?

Posted by Daniel Kulp <dk...@apache.org>.
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.

Dan



On Jan 8, 2014, at 12:48 PM, dhogan <di...@forgerock.com> 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
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon ws-publish?

Posted by dhogan <di...@forgerock.com>.
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.

Re: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon ws-publish?

Posted by dhogan <di...@forgerock.com>.
Yes, I think I can. I will create a stripped-down .war with just the relevant
classes. The effort should either give you a reproducible test, or show me
what I am doing wrong :-).

Will report back in a few hours.

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-tp5738355p5738395.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon ws-publish?

Posted by Daniel Kulp <dk...@apache.org>.
Any chance you can create a small example?   This definitely concerns me as it should work fine provided all the appropriate jars are updated.

Dan


On Jan 8, 2014, at 10:28 AM, dhogan <di...@forgerock.com> wrote:

> Thanks for the response.
> 
> Yes, cxf-rt-bindings-soap-3.0.0-milestone1.jar is in WEB-INF/lib. As is
> cxf-rt-bindings-xml-3.0.0-milestone1.jar, FWIW.
> 
> 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-tp5738355p5738392.html
> Sent from the cxf-user mailing list archive at Nabble.com.

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

RE: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon ws-publish?

Posted by dhogan <di...@forgerock.com>.
Thanks for the response.

Yes, cxf-rt-bindings-soap-3.0.0-milestone1.jar is in WEB-INF/lib. As is
cxf-rt-bindings-xml-3.0.0-milestone1.jar, FWIW.

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-tp5738355p5738392.html
Sent from the cxf-user mailing list archive at Nabble.com.

RE: 2.7.2->3.0.0milestone1 update yields No DestinationFactory upon ws-publish?

Posted by Andrei Shakirin <as...@talend.com>.
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:dirk.hogan@forgerock.com]
> Sent: Dienstag, 7. Januar 2014 23:28
> To: users@cxf.apache.org
> 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.