META-INF/cxf/cxf.xml is provided by CXF.
You can import the files with CXF 2.4.x but you don't need to import
them, as CXF switches to use other extension files which can be load
faster then spring configuration by default.
On Wed Aug 10 16:21:37 2011, David G wrote:
I was using 2.2.3 but changing to 2.4.0 fixed the issue. Which files
shouldn't I need to import?
Still strange though - I left the imports in beans.xml but there still
aren't any physical files anyway, are these being stepped over by CXF
and defaults applied?
-----Original Message----- From: Willem Jiang
Sent: Wednesday, August 10, 2011 1:05 AM
To: users@cxf.apache.org
Subject: Re: cxf.xml
Hi,
It looks like you are using CXF servlet transport.
Please make sure you put the cxf-core into the class path.
Which version of CXF are you using ?
If you are using CXF 2.4.x, you don't need to import all the below
resource.
On Wed Aug 10 06:09:44 2011, David G wrote:
I had a jax-ws service working ok then started messing around with
different loggers under the assumption this wouldn’t change core
functionality.
Now I try starting the server and get:
‘class path resource [META-INF/cxf/cxf.xml] cannot be opened because
it does not exist’
My beans.xml file always had the following imports which I thought was
odd but assumed CXF was creating defaults in the background:
<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" />
Does anyone know what could have happened?
Thanks
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
