updateSequence is advertized in the WCS 1.0.0 capabilities response but is not supported by the WCS server

[nsavard]

The WCS 1.0.0 server advertized the updateSequence option but does not support it.

The presence of the updateSequence parameter in the WCS 1.0.0 capabilities reponse triggers the following tests which fail:

wcs1-0-0/getcapabilities_operations/getcapabilities_request/get/kvp/2 to 7 and wcs1-0-0/getcapabilities_operations/getcapabilities_request/post/kvp/2 to 7

The capabilities request sent to the server is:

​http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs100_ogc_cite?UpDaTeSeQuEnCe=&ReQuEsT=GetCapabilities&VeRsIoN=1.0.0&SeRvIcE=WCS

[tomkralidis]

Note that #2384 should fix this.

[tomkralidis]

Checking into this further, as we support sections as well.

[tomkralidis]

r7367 now outputs correct updateSequence values. msautotest/wxs also updated in r7368

[tomkralidis]

Norm: can you check this one again? Thx

[nsavard]

Replying to tomkralidis:

Norm: can you check this one again? Thx

Tom: I'll check.

[nsavard]

Replying to nsavard:

Replying to tomkralidis:

Norm: can you check this one again? Thx

Tom: I'll check.

Tom: It seems to work now but the CITE tests failed because of the capabilities document that is not validating (wcs1-0-0/getcapabilities_operations/getcapabilities_request/get/kvp/3,5,6,7) and also there is an XPath error in two of the tests:

wcs1-0-0/getcapabilities_operations/getcapabilities_request/get/kvp/2 and 4. The XPath test is:

boolean(*[local-name()='ServiceException'][1]/*[@code="CurrentUpdateSequence"] ) and should read:

boolean(*[local-name()='ServiceException'][1][@code="CurrentUpdateSequence"] )

[tomkralidis]

Replying to nsavard:

Replying to nsavard:

Replying to tomkralidis:

Norm: can you check this one again? Thx

Tom: I'll check.

Tom: It seems to work now but the CITE tests failed because of the capabilities document that is not validating (wcs1-0-0/getcapabilities_operations/getcapabilities_request/get/kvp/3,5,6,7) and also there is an XPath error in two of the tests:

wcs1-0-0/getcapabilities_operations/getcapabilities_request/get/kvp/2 and 4. The XPath test is:

boolean(*[local-name()='ServiceException'][1]/*[@code="CurrentUpdateSequence"] ) and should read:

boolean(*[local-name()='ServiceException'][1][@code="CurrentUpdateSequence"] )

Norm: what is the exact request URL which causes this error? My tests work fine, i.e.:

(where updatesequence is equal)

​http://devgeo.cciw.ca/cgi-bin/mapserv/ecows?service=WCS&request=GetCapabilities&version=1.0.0&updatesequence=1999-10-10T11:11:11Z

[nsavard]

Replying to tomkralidis:

Norm: what is the exact request URL which causes this error? My tests work fine, i.e.:

(where updatesequence is equal)

​http://devgeo.cciw.ca/cgi-bin/mapserv/ecows?service=WCS&request=GetCapabilities&version=1.0.0&updatesequence=1999-10-10T11:11:11Z

Tom: The link is:

​http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs100_ogc_cite?UpDaTeSeQuEnCe=1&ReQuEsT=GetCapabilities&VeRsIoN=1.0.0&SeRvIcE=WCS

and I set "wcs_updatesequence" to "1" in the map file. Notice that the exception is triggered but the test failed.

[tomkralidis]

Norm: this is the expected response, and the Exception XML validates as well. Can you check w/ CITE on what the problem with the response is? It's doing what the spec says it should do.

[nsavard]

Replying to tomkralidis:

Norm: this is the expected response, and the Exception XML validates as well. Can you check w/ CITE on what the problem with the response is? It's doing what the spec says it should do.

Tom: Yes the behaviour is as expected. There is a problem with the XPath expression within these two tests. I checked with XPath Checker (Firefox plugin) and the XPath expression is incorrect. I'll send an email to the list.

[tomkralidis]

Norm: any update on this one?

[nsavard]

Replying to tomkralidis:

Norm: any update on this one?

Tom: All tests passed the test 5 because of the "behaviour" spelling.

[tomkralidis]

Thanks for the info. Can we close this one?

[nsavard]

Replying to tomkralidis:

Thanks for the info. Can we close this one?

Yes you can close it.