Hi Dan,
You mean, in cxf 2.4.x, no Spring related jar files are required?
Thanks
Steve
On 8/10/2011 9:21 AM, Daniel Kulp wrote:
On Wednesday, August 10, 2011 11:06:18 AM Prisca POLYTE wrote:
Hi,
In my case this is an extract of my configuration file
<import resource="classpath:META-INF/cxf/cxf.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-http.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-jaxws.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-xml.xml" />
<import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
As far as I know, you do need
cxf.xml, cxf-servlet.xml, cxf-extension-jaxws.xml. These files are
respectively in cxf-core.jar, cxf-rt-transports-http.jar,
cxf-rt-frontend-jaxws.jar.
With 2.4.x, most of the above are not needed. Really just the base cxf.xml
is all that's needed outside of OSGi. With 2.4.x, we stopped using Spring
to wire things internally which makes things a lot faster, makes us not need
Spring for almost any usecases, and makes it simpler as you don't need to
import a bunch of things. :-)
Dan
do you use Maven ? If you do, maven will get some of those jar files by
transitivity. But you should declare those dependencies as you use them ; it
will be clearer.
this is an extract from my pom. I also declare transitive dependencies. my
cxf version is 2.4.1
[extract start]
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-core</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-api</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-simple</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-jaxws</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-transports-http</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-bindings-xml</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-databinding-jaxb</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-common-utilities</artifactId>
<version>${cxf.version}</version>
</dependency>
[extract end]
for the other files I mentioned above see:
http://cxf.apache.org/docs/jax-ws-configuration.html
It seems that you need cxf-extension-soap.xml if you want to use
interceptors.
HTH
regards
--
Prisca
On Wed, Aug 10, 2011 at 10:21 AM, David G<djg2...@live.co.uk> 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<http://willemjiang.blogspot.com>(Engl
ish)>
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
