Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unclear error (and intrenal) error message #13

Open
monty241 opened this issue Sep 29, 2016 · 2 comments
Open

Unclear error (and intrenal) error message #13

monty241 opened this issue Sep 29, 2016 · 2 comments

Comments

@monty241
Copy link

monty241 commented Sep 29, 2016

When you execute the following URL:

https://geodata.nationaalgeoregister.nl/schelpdierenpercelen/wms

a java.lang.NullPointerException is returned:

<ows:ExceptionReport xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ows="http://www.opengis.net/ows" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0.0" xsi:schemaLocation="http://www.opengis.net/ows http://geodata.nationaalgeoregister.nl/schemas/ows/1.0.0/owsExceptionReport.xsd">
<ows:Exception exceptionCode="NoApplicableCode">
<ows:ExceptionText>java.lang.NullPointerException</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>

Since this is typically one of the first URLs tried by new developers, based upon let's try and see, it occurs during the initial confrontation so give an impression about quality.

Expectation: provide a clear error, signaling what a developer should do and what the documentation is. Also, addition of the exceptionCode would help in easily signalling the cause instead of looking in the text for specific words.

@ndkv
Copy link
Contributor

ndkv commented Oct 10, 2016

Thanks for bringing up this (well-known) issue.

Since this is typically one of the first URLs tried by new developers, based upon let's try and see, it occurs during the initial confrontation so give an impression about quality.

Agreed. I suspect this drives many non-geo/OGC developers away from the W*F family of standards.

Expectation: provide a clear error, signaling what a developer should do and what the documentation is. Also, addition of the exceptionCode would help in easily signalling the cause instead of looking in the text for specific words.

Agree 100%. I've created a super simple page demonstrating this idea: http://labs.ndkv.nl/wfs/

Implementing this idea in the real-world is somewhat of a challenge, however, as the OGC spec demands an XML response. Still, the message contained in the XML response can we much more descriptive. java.lang.NullPointerException sounds very ominous.

I've been planning to contact the GeoServer devs about this issue for a while now... your issue provides the much needed context. I'll reach out to them and get back to you.

@monty241
Copy link
Author

Thanks! I've looked at http://labes.ndkv.nl/wfs/, this one raises a 503 http://labs.ndkv.nl/wfs/?request=GetCapabilities&service=WFS

I've limited experienced; WGS84 and RD is as far as I can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants