Transports
By default, the client proxy uses the transport specified in the WSDL. The transport is not code generated and is not hard-coded into the proxy; instead, each type of transport is provided separately in a shared library, and the transport configuration file is copied to your <project-directory>\conf directory at code generation from the templates in <installdir>\conf\webservices.
Transports for clients are defined in the configuration file client-transports.xml. This file contains definitions for HTTP, HTTPS, and AJP13, and you can also create other, custom transports (Chapter 11). At runtime, the client executable processes the client-transports.xml file so it knows what transports are available to it.
You have two options to use a non-default transport with your client:
When calling the client application, specify an alternative location on the command line. If the location implies a different transport, the client uses that transport to send the message. In the client implementation, obtain a particular transport object based on its name attribute in the client-transports.xml file, and pass that transport in the call to the proxy’s make() method.
