Could you explain why the cxf.xml import is required given the technique(s)
I'm using to bootstrap these frameworks?
I will definitely try to remove the jetty dependency today - top priority
now that I got it working is to get rid of anything I don't absolutely need.
--
View this message in
I currently have an integration working in Tomcat - exposing services using
the camel-cxf endpoint e.g., cxf:/// - when deploying this to WebSphere I'm
running into some problems. I've already set the classloader to local first
parent last. There are still problems with conflicts for the rest
I already have the servlet working using this in my web.xml
servlet
servlet-nameCXFServlet/servlet-name
servlet-classorg.apache.cxf.transport.servlet.CXFServlet/servlet-class
load-on-startup1/load-on-startup
/servlet
servlet-mapping
servlet-nameCXFServlet/servlet-name
If I remove the serviceName and endpointName parameters to the cxf endpoint
and the previous errors are resolved but then it looks like it can't resolve
the service from the wsdl via servlce class - which is kind of what I
expected to happen.
// service class annotations
The problem is removing them and getting cxf to work right - I can't remove
geronimo because cxf-http and cxf-http-jetty have deps on it and I can't
remove those two because I get spring errors trying to load
META-INF/cxf/cxf.xml using only the import
resource=classpath:META-INF/cxf/cxf.xml/ in
That's what I though too about needing the cxf.xml import - but when I
remove it I get into problems. Not sure what's going on with that since I'm
using 2.7.0 as you can see. But yeah that's kind of what's annoying me
because it looks like that's what's forcing the dependencies on the other
Yeah, I just tried removing the cxf.xml import again and this is what I get.
As you can see - it's the CXFServlet that is expecting the registered bean.
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException:
*No bean named 'cxf' is defined*
at
Our Maven war module pulls various domain-service catalog modules into the
war. The war's web.xml has the CXFServlet configuration plus that web.xml
also defines the spring context listener. Only the war module's application
context contains the cxf.xml import (what I'm trying to jettison).
I've been struggling trying to resolve this incompatibility issue so I'm
reaching out here to the community to see if there is something obvious in
my dependency configs that might jump out as the problem. I'm using CXF
endpoing uri, not bean ref and wsdl-first via provider (config below). I
