Develop JAX-RPC web services clients

Subtopics

• Develop client bindings from a WSDL file for a JAX-RPC Web services client
  We can develop client bindings from a Web Services Description (WSDL) file for a JAX-RPC web services client.

• Changing SOAP message encoding to support WSI-Basic Profile
  Support for Universal Transformation Format (UTF)-16 encoding is required by the WS-I Basic Profile 1.0. WebSphere Application Server conforms to the WS-I Basic Profile 1.1. UTF-16 is a kind of unicode encoding scheme using 16-bit values to store Universal Character Set (UCS) characters. UTF-8 is the most common encoding used on the Internet and UTF-16 encoding is typically used for Java and Windows product applications. We can change the encoding in a SOAP message from UTF-8 to UTF-16.

• Configure the JAX-RPC web services client deployment descriptor with an assembly tool
  We can configure JAX-RPC web services client deployment descriptor with an assembly tool.

• Configure the JAX-RPC client deployment descriptor for handler classes
  We can configure the JAX-RPC client deployment descriptor for user-provided handler classes.

• Configure the JAX-RPC web services client bindings in the ibm-webservicesclient-bnd.xmi deployment descriptor
  We can configure the ibm-webservicesclient-bnd.xmi deployment descriptor file with assembly tools.
• Implementing extensions to JAX-RPC web services clients
  WAS provides extensions to web services clients using JAX-RPC.