As with the other J2EE components (EJB, web) and resources (JMS
DataSources, and so on) discussed in this
book, web service implementations need to be deployed to an
application server. And, as with these other things, deploying a web
service isn’t simply putting your code up on the server. You need to
tell the web service engine how to manage your web services at
The web service engine is responsible for accepting SOAP requests from clients, converting them into appropriate method calls on your Java implementation code , and taking the results of those method calls and converting them into the appropriate SOAP responses to the clients. In order to do this, the web service engine needs to know the following information for each web service that you want to deploy:
What Java code implements the web service, and what aspects of the Java code should be part of the web service?
How should the Java entities in your service implementation (interfaces, data objects, exceptions, etc.) be converted into SOAP/XML entities and vice versa? This covers both the description of your web service in the form of a WSDL document and conversions between SOAP entities and Java entities at runtime when operations are invoked.
This information is provided in the form of deployment descriptors and/or configuration files. These typically include:
This file defines the web ...