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

Revised: 18 Oct 2004

Supported Operating Systems and Required Software

This release implements the Java^TMfor XML-based RPC 1.1 Specification. In addition to the features required by the specification, this release provides the following:

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.)

You cannot start from an interface when using WS-I Attachment Profile 1.0. You must start with a WSDL.
Collection classes are not supported with DII and dynamic proxies.
Namespace-to-package mapping is not supported for dynamic proxies.
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 JAX-RPC 1.1 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 (section 8.2.4.1) says that a DII call.invoke method must throw a remote exception if an exception is received from the service, 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, and RemoteException.

JAX-RPC 1.1 would sometimes incorrectly mark some elements used by fault messages as nillable. This bug has been fixed in JAX-RPC 1.1.2. However, due to the non-deterministic aspect of when these elements were marked nillable, it is not possible to guarantee that the -source 1.1 or -source 1.1.1 option will be able to generate the same WSDL.
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. (4847980)
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. (4855319)
On Windows, wscompile.bat cannot parse comma-separated features on the command line. To specify features, use -f:<feature> for each feature.

Incorrect
wscompile.bat -f:feature1,feature2

Correct
wscompile.bat -f:feature1 -f:feature2
JAX-RPC cannot fully round-trip Calendar objects that have a time zone that includes a GMT offset with non-zero seconds. For example, a GMT time zone offset of GMT-11:00:04 cannot be round tripped because the XML schema dateTime format does not allow for the specification of seconds in the GMT offset.

For white papers and the latest JAX-RPC technology, go to http://jax-rpc.dev.java.net.