Axis 1.4 was packaged into four JAR artifacts: axis-saaj, axis-jaxrpc, axis and axis-ant (respectively named saaj.jar, jaxrpc.jar, axis.jar and axis-ant.jar in the Axis 1.4 binary distribution). In Axis 1.4.1, the axis JAR has been split into several smaller artifacts. This reduces the volume of code that needs to be added to the dependencies of an Axis based project and makes dependency management easier (provided that the project is built using Maven or a tool that can access Maven repositories). It also makes security auditing easier: e.g. the axis artifact contains the code for the SOAP monitor, which may be considered as a security risk if it is not properly disabled in production systems.
Nevertheless, Axis 1.4.1 also contains an all-in-one axis JAR that contains the same components as in Axis 1.4. This can be used as a drop-in replacement for the axis.jar from earlier versions, although it is strongly recommended to use the new modularized artifacts. The table below shows the relationships between the new modularized artifacts and the all-in-one JAR in Axis 1.4.1, and the artifacts included in Axis 1.4. Note that new components introduced in Axis 1.4.1 are not included in the all-in-one JAR.
I'm trying to consume an ASP.NET Webservice from a Java application. The java app is being built with Eclipse on a Windows box. I've installed the Webservice tools for Eclipse and I've downloaded the Axis 1.3 files and extracted all of the supporting .jar files (axis.jar, saaj.jar, etc) into my java\lib folder.
D:\axis\lib\axis.jar;D:\axis\lib\commons-discovery-0.2.jar;D:\axis\lib\commons-logging-1.0.4.jar;D:\axis\lib\jaxrpc.jar:D:\axis\lib\saaj.jar;D:\axis\lib\log4j-1.2.8.jar;C:\Program Files\Java\external-libs\xml-apis.jar;C:\Program Files\Java\external-libs\xercesImpl.jar;D:\axis\lib\wsdl4j-1.5.1.jar;D:\axis\lib\axis-ant.jar
After read other posts about this subject, I tried to move the "axis.jar" from my "lib" folder in the project to "JbossHome/standalone/lib/ext/". The error changed, but Jboss was no more able to load axis.
The NetSuite Web service implementation requires the client application to support multiple cookies on one line, as is the standard for cookies. There is a bug in Apache Axis that puts each cookie on its own line in the HTTP Headers. The patch version of the axis.jar fixes this problem. After it is downloaded, replace the existing axis.jar file in the lib directory of your Axis root directory with this version.
In order to compile the Java client I had to set up an Eclipse project. I createda project named "AxisTest", and imported the axis.jar, jaxrpc.jar, commons-logging.jar,commons-discovery.jar, and saaj.jar archives from the Axis distribution.After compiling the source file, I ran it and received data from the service. TheJava client was a success.