Hello,
I've been using CXF since the very, very early days and it has been rock
solid for me. Thank you.
I was putting together a tutorial for my company and wanted to use CXF
2.3.0. Unfortunately, I found that java2wsdl no longer works out of the
box. It fails to find Velocity libraries. I discovered that the
velocity jar is not in the 2.3.0 distribution. I also found that
wsdl2java fails with JDK 1.5 due to a missing jaxb-api jar. That's not
as big a deal-I should be using JDK 1.6 anyway.
As an exercise, I looked at the WHICH_JARS file and noted the jars that
are required for various CXF workflows, but not packaged with CXF 2.3.0.
The following is the contents of that file, but with only the MISSING
jars listed:
The following jars are required for all CXF usage:
- geronimo-annotation.jar (Or the Sun equivalent) [6]
- geronimo-javamail.jar (Or the Sun equivalent) [6]
(MAY be able to remove javamail if you don't use any MTOM/SAAJ type
things)
- geronimo-stax-api.jar (Or the Sun equivalent) [6]
- jaxb-api.jar [6]
- XmlSchema.jar
- woodstox-core-asl.jar [6] or another StAX implementation
- stax2-api-3.0.1.jar [6] for woodstox above
- wsdl4j.jar
For Java2WSDL and WSDL2Java:
- velocity.jar
- oro.jar
- commons-collections.jar
- commons-lang.jar
For standalone HTTP support:
- geronimo-servlet.jar
- jetty-*.jar
For Aegis support:
- jdom.jar (optional, if you want to map xsd:anyType to JDOM)
For JAX-RS support:
- abdera* (optional: for AtomPub support, but also needed for the
Management log browser console)
- commons-codec.jar (Needed for Abdera)
- jaxen.jar (Needed for Abdera)
- axiom* (Needed for Abdera)
Were these dependencies purposely excluded from the distribution (to
keep the size smaller)? Or was this an oversight?
For now, I am basing my tutorial on 2.2.11 rather than giving the
readers a longer list of things to download...
Thanks,
Chris
