You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by "Gamble, Wesley (WG10)" <WG...@tmw.com> on 2007/10/02 01:43:47 UTC
Spring framework overhead and required libraries
All,
I have a couple of questions regarding my fairly simple CXF client:
1) I notice quite a bit of Spring framework stuff in the output
when I test my client. How much overhead from Spring am I buying into
with CXF? While I'd prefer to use it over Axis1, I'm a little concerned
that CXF could be more heavyweight. To be fair, I haven't benchmarked
the 2 implementations yet so I don't have any data. Just trying to get
a feel for it.
2) Has anyone figured out the minimal set of CXF libraries
required at runtime for a client? I bet I don't need 46 JAR files to
make this thing run. Like, for example, I bet I don't need Geronimo...
Thanks,
Wes
Re: Spring framework overhead and required libraries
Posted by Daniel Kulp <dk...@apache.org>.
On Monday 01 October 2007, Gamble, Wesley (WG10) wrote:
> 1) I notice quite a bit of Spring framework stuff in the output
> when I test my client. How much overhead from Spring am I buying into
> with CXF? While I'd prefer to use it over Axis1, I'm a little
> concerned that CXF could be more heavyweight. To be fair, I haven't
> benchmarked the 2 implementations yet so I don't have any data. Just
> trying to get a feel for it.
There's definitely a startup cost involved as a BUNCH of XML files need
to be parsed, processed, etc.... Once the Bus is up and running, it's
pretty much out of the way. The benifits of being able to use spring
to configure things definitely outways the startup cost.
That said, for "simple" cases, you can use CXF clients without Spring.
Remove the spring jars and it should work.
> 2) Has anyone figured out the minimal set of CXF libraries
> required at runtime for a client? I bet I don't need 46 JAR files to
> make this thing run. Like, for example, I bet I don't need
> Geronimo...
Well, most likely you DO need the geronimo jars that we ship. Those
jars are Apache Licensed replacements for some of the Sun jars.
geronimo-annotation_1.0_spec-1.1.jar - jsr250.jar
geronimo-ws-metadata_2.0_spec-1.1.1.jar - jsr181
geronimo-activation_1.1_spec-1.0-M1.jar - activation.jar
geronimo-javamail_1.4_spec-1.0-M1.jar - mail.jar
geronimo-servlet_2.5_spec-1.1-M1.jar - servlet.jar
geronimo-jms_1.1_spec-1.1.jar - jms-api.jar
If you don't use JMS, you could get rid of the jms one. The rest are
most likely required. The first is used for configuration stuff
throughout CXF. The second is used for jaxws frontend. (if you use
aegis+simple frontend, you MAY be able to get rid of it) The next two
are required for Soap W/Attachments as well as any SAAJ things. The
servlet is required for Jetty.
If you don't use ws-security, you could get rid of xalan, xml-apis,
xmlsec, wss4j. The velocity jars are just used by tooling (not needed
for runtime). There may be others that could be pulled depending on
what you need, but not many.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog