Set the webservices.xml deployment descriptor for handler classes
Use an assembly tool to configure the webservices.xml deployment descriptor for user-provided handler classes.
Configure deployment descriptors with assembly tools provided with the appserver.
A handler class is a class that is written to modify a SOAP message that represents a remote procedure call (RPC) request or response. Handlers can be associated with a Web service or a Web service client.
Similar to JAX-RPC Web services, we can use deployment descriptors to describe Java API for XML Web Services (JAX-WS) Web services. For JAX-WS Web services, the use of the webservices.xml deployment descriptor is optional because we can use annotations to specify all of the information contained within the deployment descriptor file. Use the deployment descriptor file to augment or override existing JAX-WS annotations. Any information that you define in the webservices.xml deployment descriptor overrides any corresponding information specified by annotations.
To complete this task, we need an EAR file for the applications that you want to configure. For some handler use, such as logging or tracing, only the server or client application require configuration. For other handler use, including sending information in the SOAP headers, the client and server applications must be configured with symmetrical handlers.
The modules in the EAR file contain the handler classes to configure. These classes implement the javax.xml.rpc.handler.Handler interface.
See on writing handler classes, see chapter 6 of the Web Services for Java EE specification. See chapter 9 in the JAX-WS spec or chapter 12 in the JAX-RPC spec for additional information on the handler framework for the model. The application modules must contain the webservices.xml deployment descriptor. See the Web services specifications and API documentation to review the JAX-RPC spec along with a complete list of the supported standards and specifications.
- Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.
- If we have not done so already, configure the assembly tool so that it works on Java EE modules. we need to make sure that the Java EE and Web categories are enabled. Read about configuring the assembly tool in the Rational Application Developer documentation.
- Migrate the WAR files that are created with the Assembly Toolkit, Application Assembly Tool (AAT) or a different tool to the Rational Application Developer assembly tool. To migrate files, import the WAR files to the assembly tool. Read about migrating code artifacts to an assembly tool in the Rational Application Developer documentation.
- Set the client deployment descriptor. Read about the configuring the client deployment descriptor in the Rational Application Developer documentation.
Related tasks
Set the JAX-RPC client deployment descriptor for handler classes
Related
Handler class properties with JAX-RPC
Example: Set handler classes for Web services deployment descriptors