search

opengeospatial / ets-wms13

Repository for the Exectutable Test Suite for WMS 1.3.0
Apache License 2.0
2 stars 4 forks source link

ServletException thrown when attempting to view test results containing non-XML entity #28

Closed rjmartell closed 7 years ago

rjmartell commented 8 years ago

The test results cannot be displayed due to malformed markup. The root cause is 

org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 38; Character reference "&#26" is an invalid XML character.

It occurs when an XML entity is expected in response but a non-XML representation (i.e. an image) was received instead. It has been observed for tests that expect an exception report, such as bbox-minx-eq-maxx and bbox-miny-eq-maxy.

rjmartell commented 8 years ago

The fix would be to first check the content type header in the response for an acceptable XML media type. This applies to all tests that expect an exception report. See #20.

dstenger commented 8 years ago

Can you provide a test server which can be used to test a fix?

dstenger commented 8 years ago

Fix can be done as proposed by @rjmartell. Testing is not possible as no public available test server exists.

bermud commented 8 years ago

@keshav-nangare, please take a look a this issue, it seems is a TEAM Engine issue.

keshavnangare commented 8 years ago

I tried to reproduce this issue but not able to reproduce it, tested with the WMS13-1.19-SNAPSHOT and teamengine 4.6.

Tested with the following services:

  1. http://cite.deegree.org/deegree-webservices-3.3.14-2/services/wms?service=WMS&request=GetCapabilities
  2. http://cite.demo.opengeo.org:8080/geoserver_wms13/wms?service=wms&request=getcapabilities&version=1.3.0 3.http://services.interactive-instruments.de/cite-xs-46/cite/cgi-bin/wms/wms/wms?request=GetCapabilities&version=1.3

The all above services are successfully passed.

wms13_result_

The testing server is not available which will return a non-XML representation (i.e. an image) in response for the test bbox-minx-eq-maxx and bbox-miny-eq-maxy

bermud commented 8 years ago

I will close this issue. Seems the fix didn't cause any issues and we don't have any server to test that we can replicated this error.

dstenger commented 7 years ago

Reopened as issue was reported again: #45

dstenger commented 7 years ago

A fix was implemented and a pull request created: #49 It will be merged to master branch prior to the next release if all tests of the fix are successful.