Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOAP response is not evaluated correctly for describeAllFeatureTypes #23

Closed
geszter opened this issue Feb 24, 2016 · 1 comment
Closed
Assignees

Comments

@geszter
Copy link

geszter commented Feb 24, 2016

When SOAPEncoding is set to true, the request is made as a SOAP request, however, the response is not evaluated accordingly and fail. According to the specification when a DescribeFeatureType request is made as a SOAP request, the response should be base64 encoded, but the test evaluates this as a failure.

<test-method status="FAIL" signature="describeAllFeatureTypes(org.opengis.cite.iso19142.ProtocolBinding)[pri:0, instance:org.opengis.cite.iso19142.simple.DescribeFeatureTypeTests@4333e4a7]" name="describeAllFeatureTypes" duration-ms="307" started-at="2016-02-15T09:21:14Z" description="See ISO 19142: 9.2.4.1" data-provider="protocol-binding" finished-at="2016-02-15T09:21:15Z">
          <params>
            <param index="0">
              <value>
                <![CDATA[SOAP]]>
              </value>
            </param>
          </params>
          <exception class="java.lang.AssertionError">
            <message>
              <![CDATA[Document element has unexpected [local name]. expected [schema] but found [DescribeFeatureTypeResponse]]]>
            </message>
          </exception> <!-- java.lang.AssertionError -->
          <reporter-output>
          </reporter-output>
@rjmartell
Copy link
Contributor

Noted in D.4.5 (Encoding XML Schema in a SOAP Body), although how including an XML Schema in the SOAP message body "may cause several problems" is a mystery. A Base64 encoding is usually reserved for binary resources.

However, the type reference is invalid: there is no xsd:base64 datatype defined in XML Schema--presumably this is supposed to be xsd:base64Binary.Furthermore, this case is not referenced in cl. 9.3 nor is DescribeFeatureTypeResponseType defined in wfs.xsd.

A specification change request would seem to be required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants