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.
There is no easy way to turn off these messages (that reveal details of
your database or the structure of the geoserver app). We know what to do
from a project standpoint, but lack funds/mandate to make it happen.
Incidentally this is the same approach used by the darn oracle driver which
makes Java developers uncomfortable every time they catch an oracle
exception and have to look up the ORA number to decide how to react.
TLDR: Your security guys won't be happy, but you turn off verbose logging
for a small improvement
Jody Garnett
On Thu, Jun 5, 2014 at 8:06 PM, Andrea Aime <[email protected]>
wrote:
> On Thu, Jun 5, 2014 at 11:50 AM, Rahkonen Jukka (Tike) <
> [email protected]> wrote:
>
>> Hi,
>>
>>
>>
>> The service exceptions may also contain messages from the java code for
>> example NPE messages or something like this
>>
>>
>>
>> <?xml version="1.0" ?>
>>
>> <ServiceExceptionReport
>>
>> version="1.2.0"
>>
>> xmlns="http://www.opengis.net/ogc";
>>
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>
>> xsi:schemaLocation="http://www.opengis.net/ogc
>> http://schemas.opengis.net/wfs/1.0.0/OGC-exception.xsd";>
>>
>> <ServiceException>
>>
>> java.lang.RuntimeException: Parsing failed for DIAMETRE:
>> java.lang.NumberFormatException
>>
>> Parsing failed for DIAMETRE: java.lang.NumberFormatException
>>
>> null
>>
>> </ServiceException></ServiceExceptionReport>
>>
>>
>>
>> In this case the content of the message may be as WFS 1.0.0 standard puts
>> it “The content of the element is an exception message
>>
>> that the service wished to convey to the client application”.
>>
>
> Unfortunately many exceptions are not classified in a way that lets the
> code know if the issue was a user problem or
> an internal error, so all we can do to hide the details without
> significant refactoring is to tell the user "something went wrong" ...
> which of course would not be that useful.
>
> 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
>
>
------------------------------------------------------------------------------
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
