Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-588

Invalid array marshalling used in MarshallRpcLiteralTestCase

XMLWordPrintable

      At some point in time the ws4ee-deployment.xml file was removed from the array marshalling tests. The tests actually succeed but that is only because both the client and server are producing invalid soap messages.

      The schema definition is:
      <complexType name="booleanArray">
      <sequence>
      <element maxOccurs="unbounded" minOccurs="0" name="value" type="boolean"/>
      </sequence>
      </complexType>

      The correct request message for echoBooleanArray should be:
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mar="http://org.jboss.webservice/marshalltest-rpclit">
      <soapenv:Body>
      <mar:echoBooleanArray>
      <arrayOfboolean_1>
      <value>true</value>
      <value>false</value>
      <value>true</value>
      </arrayOfboolean_1>
      </mar:echoBooleanArray>
      </soapenv:Body>
      </soapenv:Envelope>

      However if you look at the wire, you will see the following (notice item, instead of value):

      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body>
      <ns1:echoBooleanArray xmlns:ns1="http://org.jboss.webservice/marshalltest-rpclit">
      <arrayOfboolean_1 xsi:type="soapenc:Array" soapenc:arrayType="xsd:boolean[3]" xmlns:ns2="http://org.jboss.webservice/marshalltest-rpclit/types/arrays/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
      <item>true</item>
      <item>false</item>
      <item>true</item>
      </arrayOfboolean_1>
      </ns1:echoBooleanArray>
      </soapenv:Body>
      </soapenv:Envelope>

            tdiesler@redhat.com Thomas Diesler
            jgreene@redhat.com Jason Greene
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: