If possible yes... although what we really need to do is have the
deprecated reflector delegate to the new reflector. Which should be
doable... just have to find the time :). So i leave it to you. If its
easy, sure, if not dont worry about it.
-Justin
Wayne Fang wrote:
> Hi Justin,
>
> Thank
Hi Justin,
Thanks for the response. So should I make my changes to the
wms.servlets.KMLReflector as well, knowing that it is deprecated but
still in use?
Thanks,
Wayne
Justin Deoliveira wrote:
> Hi Wayne,
>
> While deprecated, the wms.servlets.KMLReflector is still used
> unfortunatly. Its a
Hi Wayne,
While deprecated, the wms.servlets.KMLReflector is still used
unfortunatly. Its a bit of a mess. But the non-servlet reflector should
be reachable via "/kml/wms". Example:
http://localhost:8080/geoserver/kml/wms?layers=topp:states
wheras the servlet based reflector is at:
localhost:
Hi all,
I'm working on a feature that will add an optional format_options item
and have been digging around the code. I can recognize a new item when
using a full wms request by adding stuff to the FormatOptionsKvpParser
and the applicationContext.xml. The problem comes when I try to use a
k
