When using the Java version of Axis, there are two ways to expose Java code as Web service. The easiest one is to use Axis native JWS (Java Web Service) files. Another way is to use custom deployment. Custom deployment enables you to customize resources that should be exposed as Web services.
See also Apache Axis2.
JWS files contain Java class source code that should be exposed as Web service. The main difference between an ordinary java file and jws file is the file extension. Another difference is that jws files are deployed as source code and not compiled class files.
The following example will expose methods add and subtract of class Calculator.1
Once the Axis servlet is deployed, you need only to copy the jws file to the Axis directory on the server. This will work if you are using an Apache Tomcat container. In the case that you are using another web container, custom WAR archive creation will be required.
JWS Web service is accessible using the URL http://localhost:8080/axis/Calculator.jws. If you are running a custom configuration of Apache Tomcat or a different container, the URL might be different.2
Custom Web service deployment requires a specific deployment descriptor called WSDD (Web Service Deployment Descriptor) syntax. It can be used to specify resources that should be exposed as Web services. Current version (1.3) supports
When a Web service is exposed using Axis, it will generate a WSDL file automatically when accessing the Web service URL with ?WSDL appended to it.
"Apache Axis – User's Guide". axis.apache.org. Retrieved 2018-11-22. https://axis.apache.org/axis/java/user-guide.html#Publishing_Web_Services_with_Axis ↩
"Apache Axis2 – ADB - Howto". axis.apache.org. Retrieved 2023-09-19. https://axis.apache.org/axis2/java/core/docs/adb/adb-howto.html ↩