Closed bangph closed 2 years ago
Thank you for reporting. We will do further investigation.
The error can also be reproduced on a local environment.
Following StackTrace is logged: log.txt
It seems that following request body returns an image (extracted from the test).
<proc:ProcessCoverages
xmlns:wcs="http://www.opengis.net/wcs/2.0"
xmlns:gml="http://www.opengis.net/gml/3.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:proc="http://www.opengis.net/wcs_service-extension_processing/2.0"
service="WCS" version="2.0.1">
<proc:query>
for c in ( <xsl:value-of select="$CoverageId"/> )
return encode (c, "png")
</proc:query>
</proc:ProcessCoverages>
However, the test expects XML.
@bpross-52n Can you please do further investigation?
@dstenger thanks for your quick investigation. I'm not sure if the test suite for WCS Processing has changed recently or not. I hope @bpross-52n can have some ideas soon.
No, this code has not been changed for a long time (last commit is from 2015). Can you recall if you were able to pass this test in the past?
@dstenger yes, last year I ran it for renewing OGC CITE certificates without problem. Not sure what is wrong here.
@dstenger FYI: I'm using a new software version on http://conformance.rasdaman.com/rasdaman/ows?service=WCS&version=2.0.1&request=GetCapabilities. I can check an older version of it which passed this requirements last years as well. It may give some ideas.
@dstenger I think the reason is, this req15-17 needs to have SOAP body to wrap the binary content. That doesn't exist in our new software and I will fix that.
SOAP:
https://www.informit.com/articles/article.aspx?p=327825&seqNum=17
I will close this ticket.
I use this endpoint http://conformance.rasdaman.com/rasdaman/ows?service=WCS&version=2.0.1&request=GetCapabilities to test WCS WCPS 2.0 (Processing).
It failed in reqd15-17 with strange error in teamengine:
I tried to understand what it tested, here it just sends a WCPS query which encode in PNG.
@dstenger can you please give some ideas with that? The java exception is not useful for me to know what is wrong.