Hi, I think the reason these extensions are not picked up is that you prefer not to use Spring libraries. I believe spring libraries are pulled in indirectly in the demo case.
I think you may be able to overcome it like this, before calling bean.create() : BindingFactoryManager manager = bean.getBus().getExtension(BindingFactoryManager.class); manager.registerBindingFactory(JAXRSBindingFactory.JAXRS_BINDING_ID, new JAXRSBindingFactory()) give it a try please... cheers, Sergey Kruntz wrote: > > > Sergey Beryozkin wrote: >> >> Did you get it working ? For some reasons the extensions located on >> META-INF/cxf are not picked up in your case. >> Are you using Maven ? >> > > No, I'm not using Maven. > I set up a project in Eclipse whith Jetty embedded and put cxf jars into > it. > This is the list of cxf jars I'm using: > > cxf-2.2.2.jar > jra-1.0-alpha-4.jar > xml-resolver-1.2.jar > XmlSchema-1.4.5.jar > jaxb-impl-2.1.9.jar > neethi-2.0.4.jar > wsdl4j-1.6.2.jar > jsr311-api-1.0.jar > commons-codec-1.3.jar > commons-httpclient-3.1.jar > > Using Eclipse plugin "Classpath Helper", I can confirm that META-INF/cxf > *is* in the classpath of my project. > > Which are the classes and methods where the extensions are loaded? I could > try to trace it... > > Many thanks for your interest in my problem... > > -- View this message in context: http://www.nabble.com/-CXF-2.2.2--JAXRS--No-binding-factory-for-namespace-http%3A--apache.org-cxf-binding-jaxrs-registered.-tp23880630p23924981.html Sent from the cxf-user mailing list archive at Nabble.com.
