Developing JAX-RPC web services clients
次主題
Developing client bindings from a WSDL file for a JAX-RPC Web services client
You 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 that is used on the Internet and UTF-16 encoding is typically used for Java™ and Windows product applications. You can change the encoding in a SOAP message from UTF-8 to UTF-16.Configuring the JAX-RPC web services client deployment descriptor with an assembly tool
You can configure JAX-RPC web services client deployment descriptor with an assembly tool.Configuring the JAX-RPC client deployment descriptor for handler classes
You can configure the JAX-RPC client deployment descriptor for user-provided handler classes.Configuring the JAX-RPC web services client bindings in the ibm-webservicesclient-bnd.xmi deployment descriptor
You can configure the ibm-webservicesclient-bnd.xmi deployment descriptor file with assembly tools.Implementing extensions to JAX-RPC web services clients
WebSphere Application Server provides extensions to web services clients using the Java API for XML-based RPC (JAX-RPC) programming model.


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=container_wbsjaxrpc_goal_developing_clients
檔名:container_wbsjaxrpc_goal_developing_clients.html