On Tue, Jun 18, 2013 at 7:46 PM, Andrea Aime
<[email protected]>wrote:
> My next step is to go through each page of the documentation about KML and
> manually try each request and parameter described there, comparing it with
> the outputs of the old module, to make sure there are no regressions (and
> then create a geosearch2 that leverages the kml2 module).
>
Looked into the GeoSearch module and found out it's all rest config and
user interface, there are no kml generation bits in there.
So all that's needed, once the new kml2 module graduates, is to move the
geosearch specific kml generation bits (3 classes, one abstract class and
two placemark decorators) to the geosearch module so that they do activate
only when the geosearch module is added to the install GeoServer
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it 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
-------------------------------------------------------
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel