If anyone is going to try this they should realize that their testing
may miss code paths which bring in more jars, so the deployed
application may continue to have ClassNotFoundExceptions at any time.
The real answer is for the developers to classify the jars into
build-time and run-time categories, and by features used.
AFAIK, the following jars should be build-time only:
axis2-adb-codegen
axis2-codegen
jaxb-xjc
jibx-bind
This jar should only be needed if you're using ADB:
axis2-adb
These jars should only be needed if you're using JiBX:
axis2-jibx
jibx-run
These jars should only be needed if you're using XMLBeans:
axis2-xmlbeans
xbean
These jars should only be needed if you're using JAXB or JAX-WS:
axis2-jaxbri
axis2-jaxws
axis2-jaxws-api
jaxb-api
jaxb-impl
That still leaves a bunch of other ones where I'm not certain of the
uses, including:
annogen
axis2-fastinfoset
axis2-json
axis2-metadata
axis2-spring
jaxen
jettison
neethi
woden
XmlSchema
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Rich Adili wrote:
Anin,
I recently went through this exercise. I agree that the jar set is
rather large for deploying a product. My prototype deployment resulted
in a ZIP file of 25 Mbytes. I went through a rather painful trimming
process and only got it down by about half. Below is the advice I
received when I asked this question. It's a painful process to say the
least and requires testing to ensure you haven't missed something.
If you use Ant for your compilation/builds, you specify the precise
classpath (JAR's needed) when building your app. If you are missing any
JARs, compilation errors will occur. You can keep pulling out JARs and
testing their use by recompiling the application each time.
This will not work, however, for JARs needed by the JARs that you
include in your classpath. After doing the above, you'll need to test
the application and check for ClassNotFoundExceptions, and then add in
the needed JARs accordingly.
Rich Adili
-----Original Message-----
From: Anin Mathen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 22, 2007 2:24 PM
To: axis-user@ws.apache.org
Subject: Axis2 Dependency List
Guys,
I am trying to find a wiki or document that lays out the mandatory
and the optional jars in the Axis2 Standard or War distribution. I know
that I am only interested in certain features of the Axis2
implementation and would like to only bundle jars that aid in that
feature. Just to cite an example, I am only interested in plain
webservices with say HTTP as the transport mechanism. Can I take out the
huge set of jars in the standard distro and package only relevant ones.
Some advice would be appreciated.
Thanks,
Karmayogi
________________________________________________________________________
____________Sick sense of humor? Visit Yahoo! TV's
Comedy with an Edge to see what's on, when.
http://tv.yahoo.com/collections/222
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
