users@jax-rpc.java.net

JAXRPC SI binary patch

From: Doug Kohlert <Doug.Kohlert_at_Sun.COM>
Date: Tue, 03 Feb 2004 10:06:24 -0800

JAXRPC 1.1.03 binary patch has been released to java.net and can
be retrieved at the following location: https://jax-rpc.dev.java.net/patch.html.
This patch addresses the following bugs.

The first bug deals with verifying the version of model files generated
by wscompile. The JAXRPC 1.1 SI only verifies the major and minor version numbers
when doing the import of a model file. The bug fix takes into account the
major.minor.minor(patch) level of the version as well.

The second bug deals with the incorrect ordering of extensibility elements
(soap:operation and soap:binding)

As per wsdl schema [1] soap:binding and soap:operation should be the
first child of wsdl:binding and wsdl:operation respectively (and second
if there is wsdl:documentation).

JAX-RPC SI generates the wsdls with soap:binding as the last child of
wsdl:binding and soap:operation as the last child of wsdl:operation.
Which is invalid as per the wsdl schema [1].

for example:

<wsdl:binding name="HelloIFBinding" type="tns:HelloIF">
    <wsdl:operation name="echoValueType">
      <wsdl:input>
        <soap:body use="literal" namespace="http://hello.org/wsdl"/>
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" namespace="http://hello.org/wsdl"/>
      </wsdl:output>
(*) <soap:operation soapAction=""/>
    </wsdl:operation>
(*) <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
         style="rpc"/>
   </wsdl:binding>


With the fix JAX-RPC will generate:

<wsdl:binding name="HelloIFBinding" type="tns:HelloIF">
(*) <soap:binding
transport="http://schemas.xmlsoap.org/soap/http"
        style="rpc"/>
    <wsdl:operation name="echoValueType">
(*) <soap:operation soapAction=""/>
      <wsdl:input>
        <soap:body use="literal" namespace="http://hello.org/wsdl"/>
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" namespace="http://hello.org/wsdl"/>
      </wsdl:output>
    </wsdl:operation>
   </wsdl:binding>


The third bug deals the JAXRPC SI incorrectly generating an empty parameterOrder
(parameterOrder="") attribute.

As per the wsdl schema [1], the parameterOrder attribute is of type
xsd:NMTOKENS, which is defined as a list of xsd:NMTOKEN, items of length
>= 1.
JAX-RPC generates parameterOrder="" where it should not generate
parameterOrder attribute.

[1]: http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd

-- 
Doug Kohlert
Java Software Division
Sun Microsystems, Inc.
phone: 503 345-9806
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net