Java^TM API for XML-based RPC (JAX-RPC) 1.1 FCS
Release Notes

Revised: 8 October 2003

The latest updates to this document are in the online Release Notes posted on our web site.

Contents

• Supported Operating Systems and Required Software
• What This Release Includes
• What's New in This Release
• Current Limitations
• Known Bugs
• Notes for Users of the 1.0 FCS Release

Supported Operating Systems and Required Software

What This Release Includes

• Serializers and deserializers for most Collection types
• Configurable support for SSL-based authentication
• Data binding for rpc and document literal operations
• Support for these types: xsd:any, xsd:anyType, xsd:IDREF (to allow for strict compliance to the specs, support for these types is disabled when wscompile is run with the -f:strict option.)

What's New in This Release

• Support for rpc/literal and document/literal from both WSDL and service endpoint interface
• WS-I Basic Profile 1.0 support (Run wscompile with the -f:wsi option.)
• Improved schema binding
• Support for one-way operations
• DII and dynamic proxy support for rpc/literal and document/literal
• Exceptions and Value Types from the java and javax packages are now supported. (e.g. java.io.IOException).
• New option -source <version> generates code for the specified JAX-RPC SI version. Supported versions are: 1.0.1, 1.0.3 and 1.1 (default).
• New wscompile option -f:donotoverride doesn't regenerate any classes that exist in its classpath.
• wscompile Ant task supports fork option to run wscompile in a separate virtual machine.

Current Limitations

• There is a bug that affects non-Windows platforms in this tutorial example file:
  <INSTALL>/jwstutorial12/examples/jaxrpc/common/targets.xml
  To fix targets.xml, make the following changes with a text editor:
  1. Change this line:
     <condition property="wscompile" value="${wscompile.dir}/wscompile">
     To this line:
     <condition property="wscompile" value="${wscompile.dir}/wscompile.sh">
  2. Change this line:
     <condition property="wsdeploy" value="${wsdeploy.dir}/wsdeploy">
     To this line:
     <condition property="wsdeploy" value="${wsdeploy.dir}/wsdeploy.sh">
• Collection classes and attachments are not supported in document/literal or rpc/literal.
• Namespace-to-package mapping is not supported for dynamic proxies.
• Inner classes must be static.
• There is no support for GIF encoding as part of attachments. (However, decoding is supported.)
• The gen:client and gen:both options of wscompile will fail if the service name in the configuration file, the package name, and the interface name are identical.
• The implementation of dynamic proxy and DII does not support multi-dimensional arrays for doc/literal and rpc/literal.
• This limitation concerns the return type for the javax.xml.rpc.Call.getOutputParameters method. In JAX-RPC 1.0.3 and earlier versions, the getOutputParameters method returned a Map where the keys were QNames. According to the specification section 8.2.4.1 this method should return a Map where the keys are of type String. This is also consistent with the JAX-RPC 1.1 API docs. This fix may cause backward compatabilities if the client expects the keys to be of type QName.
• While the JAXRPC 1.1 Specification says that a DII call.invoke() method must throw a remote exception if an exception is received from the service (8.2.4.1), the specification is not clear on what type of exception the dynamic proxy client may throw. Therefore, this client needs to be prepared to receive either one of these possible exceptions: ServiceSpecificException, SOAPFaultException, RemoteException.

Known Bugs

• 4847980: If there is a null parameter in a remote procedure call made by a DII or dynamic proxy client, the parameter is not serialized properly.
• 4855319: This release does not support DII and dynamic proxy for the document literal and wrapper style. It is conformant with the WS-I Basic Profile Document literal mappings.

Notes for Users of the 1.0 FCS Release

• Due to some changes to the internals of the implementation, all support classes (such as stubs, ties, serializers, etc.) generated using the tools in the 1.0 FCS release are invalid for the 1.0_01 FCS release. If you created a JAX-RPC service with the 1.0 FCS tools, to deploy and run this service on the 1.0_01 FCS release, you must re-generate the support classes with the 1.0_01 FCS tools.
• When running the wscompile tool and starting from a service endpoint interface, the overloaded method names in the generated WSDL may be different than those that were generated with the 1.0 FCS version of the tools.

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