[CITE-Forum] ExceptionReport - SOS 2.0 conformacne testing

宗岩 Rocky rocky at gis.tw
Mon May 4 03:03:44 EDT 2015

Hi David,

????Thanks for your feedback.
????You are right that the structure of exception response is ExceptionReport/Exception.
????I have fixed it and updated it to OGC Github.
It will be correct x-path in the next version when Luis updated it.
????Thanks again.

????PS. The examples on the web is incorrect.
???? http://schemas.opengis.net/sos/2.0/examples/SOAP/sosException_InvalidPropertyOfferingCombination_SOAP12Fault.xml

Tsung-Yen Lee (Rocky)
software engineer
GIS Research Center, Feng-Chia University Taiwan
[´y­z: joinFB]<http://www.facebook.com/GIS.FCU>

From: CITE-Forum [mailto:cite-forum-bounces+rocky=gis.tw at lists.opengeospatial.org] On Behalf Of Archer, David
Sent: Friday, May 01, 2015 4:28 AM
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[1]"

In context see below:

<xsl:if test="$PostEncodingIsSOAP=string('true')">
                                                                <xsl:variable name="exceptionElement" select="$exceptionReport//soap12:Detail/ows:Exception[1]" />
<xsl:if test="not($PostEncodingIsSOAP=string('true'))">
                                                                <xsl:variable name="exceptionElement" select="$exceptionReport//ows:ExceptionReport/ows:Exception[1]" />

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?quot;>
               <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.

Thank you,

David Archer
Software Developer
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.

Tel: 886-4-24516669¡BFax: 886-4-24519278
Website 	http://www.gis.tw 	
Follow us on   	 	 	https://www.facebook.com/GIS.FCU
Subscribe us  	 	https://www.youtube.com/user/gistw 	  	 	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/cite-forum/attachments/20150504/452d3e28/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4842 bytes
Desc: image001.jpg
URL: <http://lists.opengeospatial.org/pipermail/cite-forum/attachments/20150504/452d3e28/attachment-0001.jpg>

More information about the CITE-Forum mailing list