On Sun, Mar 13, 2011 at 2:18 PM, <tisham@anonymised.com> wrote:
WorldWind in typical naughty worldwind fashion sends BGCOLOR=-9999.0 to
the WMS when requesting for bil32 elevation formats from the DDS/BIL
plugin. This typically causes service exceptions as discussed here:
http://forum.worldwindcentral.com/showthread.php?t=30035
Is the BGCOLOR hexcode part of the WMS standard and mandatory ?
No, it can be avoided, but if it's provided hex is the only supported format
Can I make > the reponse more lax from within the BIL Mapresponse in the extension ?
The kvp parsers are at work way before the output formats
get even into the picture.
The class that parses bgcolor is ColorKvpParser.
I think you can write a DispatcherCallback that hijacks the parsing and error
reporting mechanism, but you have to be very careful to do so to avoid
breaking the proper error reporting mechanism in other cases.
In the init(Response) method of the DispatcherCallback you check the error,
reset it to null if it's the one coming from the bgcolor parse failing,
it is that special value, and the output format is one of the two that worldwind
is using (use the raw kvp map to check the format and bgcolor values).
Then you register that dispatcher callback as a spring bean in
applicationContext.xml
and GeoServer should automatically pick it and use it
Please be very specific in the checks above or you'll leave users making
wrong request in a world of pain (no error reporting and software blowing up
in the most unexpected ways, or just ignoring what they set).
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------