JAX-RPC Home

JavaTM API for XML-based RPC ("JAX-RPC") 1.0 EA1_01 Release Notes

This release is based on the Java API for XML-based RPC 1.0 Specifications.

Contents

• Read This Section First
• What This Release Includes
• Current Limitations

Read This Section First

If you're new to JAX-RPC, the Getting Started With JAX-RPC chapter of the tutorial is a good place to start. It briefly describes the technology in a section called "What Is JAX-RPC?" and then shows you how to build and run a simple web service. To access the tutorial, you must download and install the documentation bundle. After installation, you can find the Getting Started chapter of the tutorial in the the docs/tutorial/doc/JAXRPC.html file.

What This Release Includes

• WSDL/XML to Java Mapping - static stub/tie, and service generation from WSDL

• Java to XML/WSDL Mapping - WSDL, stub/tie, and service generation from remote interfaces (service definition interface)

• SOAP Binding - support for rpc/encoded messages as well as limited document/literal messages

• Fault handling

• Header processing

• Dynamic Invocation Interface (DII) - support for invoking SOAP operations on a service endpoint without the need for a static stub

• Basic Authentication - support for HTTP basic authentication

• Serializers/Deserializers for primitive types - serializers and deserializers are provided for many of the more standard primitive types

• Automatic generation of serializers/deserializers for JavaBeans components

• Support for xsd:anyType

• Pluggable serializers/deserializers

• Servlet-based service definition model

Current Limitiations

• No support for polymorphic arrays-- arrays that are not typed in the XML schema

• Only enumerations of strings are supported

• No session support

• No support for header faults

• Only encoded headers are supported.

• Header names must be unique within a port.

• Document/literal binding is limited to request/response messages that have exactly one part.

• SOAP Messages with attachments. These messages can be used but the reference implementation currently does not do anything with attachments.

• Dynamic Proxies are not implemented.

• SOAPActions must always be specified.

• Servlet-based service definition model is non-standard - no deployment descriptor support

• Many of the rules about "Mapping of XML names" in the specification haven't been implemented yet. In particular, you'll run into problems if you try to import WSDL documents that use names containing characters other than letters and numerals.

• No SSL (HTTPS) support

• No support for WSDL-based service configuration in DII

• No JNDI support for service classes

• When importing WSDL, all generated classes will appear within a single package.

• Service specific exceptions must have only one public constructor that has one argument. The type of this constructor must match at least one method which has a name that starts with get, takes no arguments, and returns the same type as the constructor. For example:

  
  public class MyException extends Exception {
  
      private MyType type;
  
      public MyException(MyType type) {
          this.type = type;
      }
  
      public MyType getType() {
          return type;
      }
  }
  
  

Copyright © 2002 Sun Microsystems, Inc. All rights reserved.