Apache Axis2 distributions comes with number of jars which are used in various services. Out of these 60 jar files there are only a few needs for some applications. Actually the minimum set of jars depends on the service type to be used.
Here is a list of jars required to Deploy a service created by using wsdl2java tool using ADB databinding. This jars set is taken from Axis2 1.4.1 release.
axis2-kernel-1.4.1.jar
commons-logging-1.1.1.jar
geronimo-stax-api_1.0_spec-1.0.1.jar
wstx-asl-3.2.4.jar
wsdl4j-1.6.2.jar
XmlSchema-1.4.2.jar
axiom-impl-1.2.7.jar
axiom-dom-1.2.7.jar
axiom-api-1.2.7.jar
backport-util-concurrent-3.1.jar
neethi-2.0.4.jar
commons-httpclient-3.1.jar
activation-1.1.jar
commons-fileupload-1.2.jar
woden-api-1.0M8.jar
woden-impl-dom-1.0M8.jar
httpcore-4.0-beta1.jar
axis2-adb-1.4.1.jar
commons-codec-1.3.jar
For additional binding corresponding runtime jars for that binding is required. (i.e for xmlbeans-2.3.0.jar)
Subscribe to:
Post Comments (Atom)
7 comments:
There's something conflicting between
org.apache.axiom.om.OMElement (part of axiom-api-1.2.7.jar)
org.apache.axiom.om.impl.llom.OMElementImpl (part of axiom-impl-1.2.7.jar) and Axis2 Service Archiver Plugin 1.4.0
I've explained better here -> http://wso2.org/library/1675#comment-7230
sorry for late reply.
I think you mean the eclipse Axis2 plugin. If that comes with a different axis2 version then there will be a conflict. Here what I have given is the set of jar files needed at runtime.
I haven't look at the jaxws stuff. will add that once get a time.
List was very helpful. When I deployed my service in Websphere, it complained about missing codehaus class - after adding 'annogen-0.1.0.jar', it worked fine.
awesome. this is what I was looking for.
how come something like this is not documented in axis2 website beats me.
please note that stax is a part of jdk6, so you do not need geronimo-stax-api I guess.
Post a Comment