With 2.2.4 it works fine :-)
I still mustn't add these imports:
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml /
import resource=classpath:META-INF/cxf/cxf-servlet.xml /
But I'm now able (with 2.2.4) to configure
On Fri October 16 2009 5:01:05 am Spam wrote:
With 2.2.4 it works fine :-)
I still mustn't add these imports:
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml /
import resource=classpath:META-INF/cxf/cxf-servlet.xml /
I think this is one of the bugs I fixed in 2.2.4. If made some modifications
to the cxf:bus processing stuff to grab the default bus (which is what you
see being created) if one isn't already in the context. Thus, this may be
fixed in 2.2.4 (which is being voted on now)
Dan
On Tue
In my 'web.xml' I load services related configuration with:
servlet
servlet-nameCXFServlet/servlet-name
display-nameCXF Servlet/display-name
servlet-classorg.apache.cxf.transport.servlet.CXFServlet/servlet-class
init-param
Hi All,
I answer by myself.
Even if I don't really know why, removing following lines from my
services configuration is fixing the issue (services are visible and are
running perfectly):
import resource=classpath:META-INF/cxf/cxf.xml /
import
I guess it kind of depends on how this config is picked up...
Is this a cxf-servlet.xml thing that the CXFServlet is loading (in which case
you shouldn't have the imports as your config is loaded on top of the
Default bus configs) or is this a applicationContext.xml type thing that
the sping
Hi All,
I've followed the guidelines from
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html; to
configure my web services inside Tomcat 6.0.
If I use the following configuration, everything in the cxf (log4j) log
file looks like the services are deployed successfully, but checking
with
