web server - Borland Technical Publications

Web Service Deployment Descriptors
Web Service Deployment Descriptors
NOTE
Web services are deployed as part of a WAR. A single WAR can contain multiple web
services. You can also deploy multiple WARs with each containing many web services.
The difference between a normal WAR and a WAR containing web services is the
presence of an extra descriptor named server-config.wsdd in the WEB-INF directory. The
server-config.wsdd file provides configuration information (the name of the web
service, the provider, any corresponding Java classes and allowed methods).
There is one WSDD file per WAR and it contains information about all available web
services within that WAR.
The typical component structure of a WAR containing web services has the following
elements:
■
WEB-INF/web.xml
■
WEB-INF/server-config.wsdd
■
WEB-INF/classes/
■
WEB-INF/lib/
The WEB-INF/lib also contains some standard JARs that are necessary for the Axis
Runtime engine.
To publish your Java classes as a web service, use the WSDD format to define the
items that you want to deploy to the Partition. For example, an entry corresponding to a
service named “BankService” can be:
In this case, the com.fidelity.Bank Java class links to web service BankService. The
class com.fidelity.Bank can have a number of public methods, but only the methods
create_account and query_account are available through the web service.
For more information on the web services deployment descriptor (WSDD), refer to the
Axis User Guide located in /doc/axis/user-guide.html.
Creating a server-config.wsdd file
To create the server-config.wsdd:
■
Use JBuilder to generate the deployment descriptor as part of your WAR.
or
1 Use a text editor to write a deploy.wsdd file. Refer to the deploy.wsdd file in
/examples/webservices/java/server.
2 Run the Apache Axis Admin tool with deploy.wsdd file (see “Tools Overview” on
page 81) by typing:
prompt>java org.apache.axis.utils.Admin server deploy.wsdd
The server-config.wsdd file is packaged as part of the WAR.
Chapter 9: Borland Enterprise Server Web Services 79