[CITE-Forum] ExceptionReport - SOS 2.0 conformacne testing
rmartell at galdosinc.com
Thu Apr 30 18:35:24 EDT 2015
According to WSC 2.0 (06-121r9, 8.7), the soap:Detail element contains ows:ExceptionReport.
So the path expression for the SOAP error response is incorrect as you pointed out.
From: CITE-Forum [mailto:cite-forum-bounces+rmartell=galdosinc.com at lists.opengeospatial.org] On Behalf Of Archer, David
Sent: Thursday, 30 April, 2015 13:28
To: cite-forum at lists.opengeospatial.org
Subject: [CITE-Forum] ExceptionReport - SOS 2.0 conformacne testing
I'm testing our software for compliance with the SOS 2.0 test suite. In particular the SOAP interface.
For exception reporting OGC 06-121 Section 8 describes and shows an <ExceptionReport><Exception> structure. But the SOAP test in the SOS_ETS.XML CTL file uses the following XPath expression to check the exception: select="$exceptionReport//soap12:Detail/ows:Exception"
In context see below:
<xsl:variable name="exceptionElement" select="$exceptionReport//soap12:Detail/ows:Exception" />
<xsl:variable name="exceptionElement" select="$exceptionReport//ows:ExceptionReport/ows:Exception" />
You will notice that the XPath expression has dropped the ows:ExceptionReport element. If this is correct could someone give me an explanation? Otherwise I believe it does not conform to the specification. You will notice the non-SOAP version does have the ows:ExceptionReport in the XPath expression.
This is in the checkExceptionReport function and effects all exception reporting in the SOS 2.0 conformance tests. At this time it is causing any exception checks in my software to fail, you can see an example of my exception message below from the GetCapabitlities tests:
<ows:ExceptionReport version="1.1.0" xml:lang="en-us" xsi:schemaLocation...">
<ows:Exception exceptionCode="InvalidParameterValue" locator="section">
<ows:ExceptionText>Request was made with an invalid section: WrongSection.</ows:ExceptionText>
If there is supposed to be a difference between the SOAP and non-SOAP version of the Exception Reporting, could someone clarify for me.
Engineering & Support Solutions Directorate
Riverside Research Institute
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain proprietary, confidential or privileged information or otherwise be protected by law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender and destroy all copies and the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CITE-Forum