You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
When you execute the following URL:
https://geodata.nationaalgeoregister.nl/schelpdierenpercelen/wms
a java.lang.NullPointerException is returned:
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.
The text was updated successfully, but these errors were encountered: