Avoid reporting a missing layer message when in fact the layer is there
-----------------------------------------------------------------------
Key: GEOS-1544
URL: http://jira.codehaus.org/browse/GEOS-1544
Project: GeoServer
Issue Type: Bug
Components: WMS
Affects Versions: 1.6.0-RC1
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 1.6.0-RC2
The cure is simple, don't build a service exception to report the layer has not been found, return null instead (in GetMapKvpReader.findXXXLayer). Only throw an exception when it's verified the layer is really not there (now we throw the exception, just to catch it right away, to notice the layer we're looking for is not a feature but a coverage).
Alternatively, avoid ServiceException to log at fine level the exception message... that looks like a silly place to log that, plus it does not log the stack trace. Better leave the client code to deal with logging, don't do that in a exception constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira