Deploying web services
Though we developed all the Java classes included in our sample hotel reservation system, we have not made them web services yet. In other words, still, our three web service implementation classes cannot be invoked by a web service client, such as soapUI. In this section, we make a deployable artifact so that we can deploy the services in a service container such as Apache Axis2.
There are multiple ways of deploying a web service in the Apache Axis2 SOAP engine. We will use the service archive-based deployment mechanism where we create a deployable archive with all service artifacts and copy that into the Axis2 server's deployment folder. In this mechanism, the deployable artifact is known as an
Axis2 Archive
(aar
).
In order to deploy an Axis2 service as an aar
file, a deployment descriptor should be included with it. The Axis2 deployment descriptor is known as services.xml
and must be placed inside the META-INF
folder of the aar
file. The services.xml
tells the Axis2...