Revised: 18 Oct 2004
See the JWSDP Release Notes.
This release implements the JavaTMfor XML-based RPC 1.1 Specification. In addition to the features required by the specification, this release provides the following:
xsd:IDREF(to allow for strict compliance to the specs, support for these types is disabled when
wscompileis run with the
javax.xml.rpc.Call.getOutputParametersmethod. In JAX-RPC 1.0.3 and earlier versions, the
getOutputParametersmethod returned a
Mapwhere the keys were
QNames. According to the JAX-RPC 1.1 Specification (section 18.104.22.168) this method should return a
Mapwhere 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
call.invokemethod 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:
-source 1.1.1option will be able to generate the same WSDL.
nullparameter in a remote procedure call made by a DII or dynamic proxy client, the parameter is not serialized properly. (4847980)
wscompile.batcannot parse comma-separated features on the command line. To specify features, use
-f:<feature>for each feature.
wscompile.bat -f:feature1 -f:feature2
Calendarobjects 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
dateTimeformat 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.
Copyright © 2004 Sun Microsystems, Inc. All rights reserved.