[Geoserver-devel] Some rest debugging headaches

[Andrea A. <and...@ge...>]

Hi,
I was writing some tests for the simple feature service implementation
when I got tangled up in a separate issue... the basic test I wrote
was failing to build a valid response, but the response status I got back
was a 200 and just a "[" as the content of the response.
No logs, no way to know what happened.

After some debugging I found that Restlet logged the exception that
was thrown only at the INFO level, which is disabled during tests,
and that it did set the status to 500, but too late because the response
was already committed.

For the first issue I'm attaching a patch that seems to solve it:
the ServletConverter gets subclassed to override the logging level
of the error to SEVERE.

For the second one (setting the status before commiting the request)
I guess we should have a output strategy
handling on the rest path, so that we cache some kb of data before
sending back a response.
I _think_ this may be doable by wrapping the httpservletresponse
into one that would build a stream backed by the output strategy

Opinions?

Cheers
Andrea


-- 
Ing. Andrea Aime
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy

phone: +39 0584962313
fax:     +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------