Changes between Version 31 and Version 32 of ZooCompliancyReport
- Timestamp:
- Sep 19, 2010, 2:31:13 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ZooCompliancyReport
v31 v32 2 2 3 3 ZOO-PSC would like to report results of tests conducted on ZOO-Kernel WPS 4 implementation. Comparis ion of some current WPS implementation was reported in4 implementation. Comparison of some current WPS implementation was reported in 5 5 presentation entitled "COMPLIANCE TESTING OF OPEN SOURCE SOFTWARE FOR WEB 6 PROCESSING SERVICES" [http://2010.foss4g.org/presentations_show.php?id=3604 link]. 7 {{{ 8 #!html 9 <!-- 10 The presentation is based on report No. CIP-ICT-PSP-2009-3-250474 entitled “Web 11 Processing Service Study” for the client/project: "BRIdging SErvices, Information and 12 Data for Europe" (BRISEIDE) [http://www.briseide.eu/ link]. 13 --> 14 }}} 6 PROCESSING SERVICES" [http://www.slideshare.net/TheodorFoerster/compliance-testing-of-open-source-software-for-web-processing-services link]. 7 15 8 Our testing details are presented in more details below. The test with ZOO WPS are 16 contrary to the presentation and report mentioned above. We call upon the authors 17 of the presentation and report referred above to make appropriate corrections in their 18 presentation and report based on the results outlined below. We hope that more well 19 planned and coordinated implementation testing can be done in the future. 9 contrary to the presentation mentioned above [http://www.slideshare.net/TheodorFoerster/compliance-testing-of-open-source-software-for-web-processing-services link]. We call upon the authors of the presentation and report referred above to make appropriate corrections in their presentation in light of our test results outlined below. We hope that more well planned and coordinated implementation testing can be done in the future. 20 10 21 11 Gérald Fenoy (Chair ZOO PSC) … … 23 13 = ZOO Project WPS testing details = 24 14 25 In above mentioned report, some unusual behaviour of the ZOO Kernel was pointed out. Hence, the ZOO PSC decided to answer to this report by making his own report about ZOO Project compliancy testing using the same way as in the report.15 In above mentioned report, some unusual behavior of the ZOO Kernel was pointed out. Hence, the ZOO PSC decided to conduct our own tests with ZOO WPS implementation using the same method reported in the FOSS4G2010 presentation. 26 16 27 17 First note about this response that we are currently preparing, we weren't able to use XMLSpy 2007 Professional version as no more Evaluation version is available, so we used the XMLSpy 2011 Professional one as we can use it for an evaluation period of 30 days. … … 31 21 == !GetCapabilities request == 32 22 33 In the section 5.5 of the report an error was pointed out about some unexpected metadata : namely Test attribute to the Metadata node getting the "Demo" value. This was due to wrong ZCFG files of the first Services we made in the begining of the 2009 year.23 In the FOSS4G2010 presentation [http://www.slideshare.net/TheodorFoerster/compliance-testing-of-open-source-software-for-web-processing-services link], an error was pointed out about some unexpected metadata : namely Test attribute to the Metadata node getting the "Demo" value. This was due to wrong ZCFG files of the first Services we made in the beginning of the 2009 year. 34 24 35 25 The provided URL to run this test is wrong, one would use this one : … … 43 33 --> 44 34 }}} 45 So for the !GetCapabilities request, the Capabilities document output by the ZOO Kernel is '''Valid'''.35 So, for the !GetCapabilities request, the Capabilities document output by the ZOO Kernel is '''Valid'''. 46 36 47 37 == !DescribeProcess request == 48 38 49 I n the section 5.11 of the report we can read that theZOO Kernel can't handle the !DescribeProcess request and output a valid !ProcessDescriptions Document. Indeed the first versions of ZOO Kernel was wrong in that, but hopefully the last one, included in OSGeoLiveDVD 4.0 returns already the valid !ProcessDescriptions document.39 It was also reported in the presentation that ZOO Kernel can't handle the !DescribeProcess request and output a valid !ProcessDescriptions Document. Indeed the first versions of ZOO Kernel was wrong in that, but hopefully the last one, included in OSGeoLiveDVD 4.0 returns already the valid !ProcessDescriptions document. 50 40 51 41 http://zoo-project.org/cgi-bin-new/zoo_loader.cgi?REQUEST=DescribeProcess&SERVICE=WPS&version=1.0.0&Identifier=Buffer … … 59 49 == Execute request == 60 50 61 In the 5.13 section of the report you can get the requestsfor Execute as XML POST requests, as it is the mandatory method.62 63 To use the XML POST requests provided in the report or easier by usingcopy/paste from this page, please follow this [http://zoo-project.org/test_services.html link] to paste in the HTML form.64 65 === section 5.17 (Synchronous call using asReference)===51 ZOO WPS provides valid response for Execute as XML POST requests, as it is the mandatory method. 52 53 To use the XML POST requests, please copy/paste from this page, please follow this [http://zoo-project.org/test_services.html link] to paste in the HTML form. 54 55 === Synchronous call using asReference === 66 56 67 57 {{{ … … 92 82 }}} 93 83 94 === section 5.18.1.4 (Synchronous call with data included)===84 === Synchronous call with data included === 95 85 96 86 {{{ … … 121 111 }}} 122 112 123 === section 5.23 (Asynchronous call with data asReference)===113 === Asynchronous call with data asReference === 124 114 125 115 {{{ … … 152 142 Here both statusLocation file and response are '''Valid'''. 153 143 154 === Section Not Found (Asynchronous call with full data included)===144 === Asynchronous call with full data included === 155 145 156 146 Even if it is not mentioned in the original report, you can also use the storeExecuteReponse="true" for !ResponseDocument with the asReference attribute for the Output settled to true as in the following request : … … 185 175 The resulting document and the statusLocation document are both '''Valid'''. 186 176 187 === section 5.28 (!RawDataOutput test)===177 === !RawDataOutput test === 188 178 189 179 {{{
