Extensions to the JAX-RPC and Web Services for J2EE programming models

WebSphere Application Server provides extensions to the Java API for XML-based RPC (JAX-RPC) and Web Services for J2EE client programming models. These extensions include:

• The REQUEST_TRANSPORT_PROPERTIES property and RESPONSE_TRANSPORT_PROPERTIES property can be added to a JAX-RPC client Stub to enable a Web services client to send or retrieve HTTP transport headers.

  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.

• Implementation-specific support for javax.xml.rpc.ServiceFactory.loadService() as described by the JAX-RPC specification. The loadService methods create an instance of the generated service implementation class in an implementation-specific manner. The loadService methods are new for JAX-RPC 1.1 and include three signatures:

  • public.javax.xml.rpc.Service loadService (Class serviceInterface)

    As documented in the JAX-RPC specification, this method returns the generated service implementation for the service interface. We can review the JAX-RPC specification through Web services: Resources for learning.

  • public.javax.xml.rpc.Service loadService (URL wsdlDocumentLocation, Class serviceInterface, Properties properties)

    This method behaves like the loadService (Class serviceInterface) because the following parameters are ignored:

    • wsdlDocumentLocation

    • properties

  • public.javax.xml.rpc.Service loadService (URL wsdlDocumentLocation, QName serviceName, Properties properties)

    This method returns the generated service implementation for the specified service by using optional namespace-to-package mapping information.

    • wsdlDocumentLocation - ignored

    • serviceName - QName (namespace, localpart) of the service

    • properties - If this parameter is non-null, it contains namespace-to-package mapping entries. Each Property entry key is a String corresponding to the namespace. Each Property entry value is a String corresponding to the Java package name.

      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 also

Sending HTTP transport headers
Retrieving HTTP transport headers
HTTP transport header properties best practices

 

---