On Thu, Jun 5, 2014 at 12:24 PM, Jody Garnett <[email protected]>
wrote:
> Yep, hence the (admittedly massive) amount of work to bust out formal
> error messages for ServiceException. GeoServer would then be stuck only
> returning the "cleaned" messages provided by an official ServiceException,
> or doing the stack trace thing showing the initial cause if "verbose"
> exceptions was turned on.
>
One observation, there is a still somewhat small but growing set of
ServiceException that are thrown setting
the locator and code, those could be already be classfied in some way,
e.g., if I see the code is InvalidSRS then
I know the error message is likely safe to return, whilst if the code is
"internalError" or not available at all,
the message might contain some information that ought to be restricted (or
maybe not... the large refactor would
indeed have to be done in order to make sure the code is available for all
exceptions, and we have a way to
know if a certain code represents a user error, or an internal error)
Cheers
Andrea
--
==
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
