WebSphere Application Server provides extensions to the Java API for XML-based RPC (JAX-RPC) and Web Services for Java 2 Platform, Enterprise Edition (J2EE) client programming models.
To learn how to modify your client code to send or retrieve transport headers see Sending HTTP transport headers or Receiving HTTP transport headers. To learn more about these properties, see HTTP transport header properties best practices.
As documented in the JAX-RPC specification, this method returns the generated service implementation for the service interface. You can review the JAX-RPC specification through Web services: Resources for learning.
This method returns the generated service implementation for the specified service by using optional namespace-to-package mapping information.
If the properties argument contains an entry with a key (namespace) that matches the namespace portion of the QName serviceName argument, the entry value (javaPackage) is used as the package name when trying to locate the service implementation.
See the related links to learn more about the topics associated with these programming model extensions.
To review the Javadoc used for APIs and SPIs, see Reference: Generated API documentation. Follow the instructions in this topic that lead you to the API and SPI interfaces.
Review the specifications for the standards and APIs used in developing Web services.