Opened 11 years ago
Closed 11 years ago
#472 closed defect (fixed)
no 'request' Parameter for WCS
Reported by: | Jinsongdi Yu | Owned by: | Dimitar Misev |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | petascope | Version: | 8.5 |
Keywords: | Cc: | Piero Campalani | |
Complexity: | Medium |
Description
The WCS post test fails due to the check for 'request' parameter
This check results in 'Bad Post Parameter' Exception for WCS Post 1.0 test. This 'request' parameter is not in the spec.
Attachments (1)
Change History (5)
by , 11 years ago
comment:1 by , 11 years ago
Cc: | added |
---|
comment:2 by , 11 years ago
It would be good to know which req. is this ticket targeting..
I tested KVP compliance to WCS service (revision r5
— latest — of the testsuite), whereas requirements 1 to 24 fail for SOAP and XML protocols.
In many (or maybe all) of the XML tests, I see the problem is:
Bad Post parameter '<?xml version', expected parameters are 'query'/'request'
Whereas for SOAP I see a lot of:
Error in call to extension function {public org.w3c.dom.NodeList com.occamlab.te.TECore.soap_request(org.w3c.dom.Document,java.lang.String) throws java.lang.Throwable}: Exception in extension function java.lang.reflect.InvocationTargetException
As far as I understood XML (and SOAP) are going to be deprecated and even removed from the available protocols, so I didn't investigate those errors.
Piero is this still valid? You said the OGC test passes.