Hi Daniel,
thx for pointing out.
Will exclude the catalog stuff as soon as i upgrade to 2.2.1. And i
also wondered why mail is there :) Perhaps i will exclude this too.
BTW i just read about the JAX-RS api in CXF and that i can simply
expose services with jax-ws AND jax-rs. Thats nice! As an old XFire
user, i am really impressed how things got even better.
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 06.04.2009 um 22:58 schrieb Daniel Kulp:
On Sat April 4 2009 9:12:58 am Marc Logemann wrote:
Hi,
i am using the CXF maven modules for deploying CXF into my app. Is
there somewhere a description which does what? Right now i am
including these modules:
cxf-rt-frontend-jaxws
cxf-rt-transports-http
Currently i am just exposing JAX-WS webservices with Spring. I hope
these two are the minimum i have to include. I am really bothering
about library jars size currently because our app gets bigger and
bigger and i am really scared how much useless stuff we ship.....
That's probably the minimum for most common use cases without
resorting to
excludes. If you aren't doing certain things, you can PROBABLY
using
excludes to exclude things. For example, if you don't use any
handlers or
dispatch/provider endpoints, you may be able to get rid of the mail
jar and
saaj stuff. With 2.2.1-SNAPSHOT, you could get rid of xml-
resolver jar if
you don't use catalogs.
Basically, per JAX-WS spec, we HAVE to include all of that stuff so
jaxws spec
compliant stuff "just works". But you can try excluding some of it.
Dan
thx for hints....
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
--
Daniel Kulp
[email protected]
http://www.dankulp.com/blog
