This topic explains how to use an assembly tool to configure the 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 2 Platform, Enterprise Edition (J2EE) specification and chapter 12 of the Java API for XML-based remote procedure call (JAX-RPC) specification available through Web services: Resources for learning. The application modules must contain the webservices.xml(for server) and the client deployment descriptors.
You must configure the assembly tool before you can use it.
Why and when to perform this task
Configure a handler in the client deployment descriptor by following the steps provided:
Steps for this task
Result
You have a client deployment descriptor that is configured.What to do next
Test the Web services client. This task explains how to test an unmanaged client Java archive (JAR) file and an unmanaged client application.Related tasks
Configuring the webservices.xml deployment descriptor for handler classes