Configuring the JAX-RPC client deployment descriptor for handler classes
You can configure the JAX-RPC client deployment descriptor for user-provided handler classes.
Before you begin
You need an enterprise archive (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 needs to be configured. For other handler use, including sending information in SOAP headers, the client and server applications must be configured with symmetrical handlers.
The modules in the EAR file should contain the handler classes to configure. These classes implement the javax.xml.rpc.handler.Handler interface. For more information on writing handler classes, see chapter 6 of the Web Services for Java™ Platform, Enterprise Edition (Java EE) specification and chapter 12 of the Java API for XML-based remote procedure call (JAX-RPC) specification. The application modules must contain the webservices.xml (for server) and the client deployment descriptors.
如需支援的標準和規格的完整清單,請參閱 Web 服務規格與 API 說明文件。
About this task
Configure a handler in the client deployment descriptor by following the steps provided:
Procedure
- Start an assembly tool. Read about starting the assembly tool in the Rational® Application Developer information.
- If you have not done so already, configure the assembly tool so that it works on Java EE modules. You need to make sure that the Java EE and Web categories are enabled. Read about configuring the assembly tool in the Rational Application Developer information.
- Migrate the web application archive (WAR) or Java archive (JAR) files that are created with the Assembly Toolkit, Application Assembly Tool (AAT) or a different tool to the Rational Application Developer assembly tool. Read about importing WAR or JAR files using an assembly tool in the Rational Application Developer information.
- Configure the client deployment descriptor. Read about creating web services handlers in the Rational Application Developer information.