RE: [wss] wss-interop1-draft-05 issue, must read before interop on Monday

["Chris Kaler" <ckaler@microsoft.com>]

Good catch otherwise we might get additional namespace declarations that
don't match the example text in the interop document.


-----Original Message-----
From: Anthony Nadalin [mailto:drsecure@us.ibm.com] 
Sent: Friday, June 06, 2003 5:52 PM
To: wss@lists.oasis-open.org
Subject: [wss] wss-interop1-draft-05 issue, must read before interop on
Monday 





During some initial testing we found a problem with the schema in the
latest interop document. The schema does have a targetNamespace (as
required by WS-I Basic Profile 1.0), w/o this you will run into
problems.
The  latest interop document (wss-interop1-draft-05) needs to be updated
to
look like the following (also attached is the file):

<definitions xmlns:tns="http://xmlsoap.org/Ping"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
targetNamespace="http://xmlsoap.org/Ping" name="Ping">
  <!--
  <types>
    <schema targetNamespace="http://xmlsoap.org/Ping"
xmlns="http://www.w3.org/2001/XMLSchema">
      <complexType name="ping">
        <sequence>
          <element name="text" type="xsd:string" nillable="true"/>
        </sequence>
      </complexType>
      <complexType name="pingResponse">
        <sequence>
          <element name="text" type="xsd:string" nillable="true"/>
        </sequence>
      </complexType>
      <element name="Ping" type="tns:ping"/>
      <element name="PingResponse" type="tns:pingResponse"/>
    </schema>
  </types>
  -->

  <types>
    <schema targetNamespace="http://xmlsoap.org/Ping"
xmlns="http://www.w3.org/2001/XMLSchema">
      <element name="text" type="xsd:string" nillable="true"/>
      <complexType name="ping">
        <sequence>
          <element ref="tns:text"/>
            </sequence>
      </complexType>
      <complexType name="pingResponse">
        <sequence>
          <element ref="tns:text"/>
            </sequence>
      </complexType>
      <element name="Ping" type="tns:ping"/>
      <element name="PingResponse" type="tns:pingResponse"/>
    </schema>
  </types>

  <message name="PingRequest">
    <part name="ping" element="tns:Ping"/>
  </message>
  <message name="PingResponse">
    <part name="pingResponse" element="tns:PingResponse"/>
  </message>

  <portType name="PingPort">
    <operation name="Ping">
      <input message="tns:PingRequest"/>
      <output message="tns:PingResponse"/>
    </operation>
  </portType>

  <binding name="PingBinding" type="tns:PingPort">
    <soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="Ping">
      <soap:operation/>
        <input>
          <soap:body use="literal"/>
        </input>
        <output>
          <soap:body use="literal"/>
        </output>
    </operation>
  </binding>

  <service name="PingService">
    <port name="PingPort1" binding="tns:PingBinding">
      <soap:address location="http://localhost:9080/pingejb/Ping1"/>
    </port>
    <port name="PingPort2" binding="tns:PingBinding">
      <soap:address location="http://localhost:9080/pingejb/Ping2"/>
    </port>
    <port name="PingPort3" binding="tns:PingBinding">
      <soap:address location="http://localhost:9080/pingejb/Ping3"/>
    </port>
  </service>
</definitions>

(See attached file: ping.wsdl)


Anthony Nadalin | work 512.436.9568 | cell 512.289.4122