Hi I've seen a very similar issue recently, which happened during a fairly specific deployment in Karaf on Unix only. Generally speaking, I believe problems like this are always caused by some cl restrictions or bugs or multiple (Spring) libs interfering, etc. Using explicit bean configuration, without depending on jaxrs: handlers, did the trick for me as a workaround till we get the underlying issue fixed, so it's something which can be tried in similar cases too:
https://cwiki.apache.org/confluence/display/CXF20DOC/JAXRS+Services+Configuration#JAXRSServicesConfiguration-ConfiguringJAXRSservicesusingexplicitbeanconfiguration thanks, Sergey > org.springframework.beans.factory.BeanDefinitionStoreException: > > Unexpected exception parsing XML document from ServletContext resource > [/WEB-INF/cxf-beans.xml]; > > nested exception is org.springframework.beans.FatalBeanException: > > Class [org.apache.cxf.jaxrs.spring.NamespaceHandler] for namespace [ > http://cxf.apache.org/jaxrs] > > does not implement the > [org.springframework.beans.factory.xml.NamespaceHandler] interface
