Hi Chris:
Andrea has been politely helping clean up some of the rendering code in
GeoTools; but has not really asked in a blunt enough fashion on the
geoserver-devel list.
The KML code is going to be need in of some serious QA and testing after this
patch; do you have any developers who would be good for the work? We could
arrange an IRC breakout session (and I could be available to answer any api
change questions).
I don't want to see this patch go ahead; and you learn about a sudden drop in
quality when taking GeoServer into production at the end of this release cycle.
Basically:
1) MapLayer was the general purpose swiss army knife of a class - it could
handle anything and you would manage to cut your self on the little pair of
scissors each time you used it
2) It has been replaced by a carving set of tools each that does one thing
explicitly
3) Lots of KML code assume everything in a Map is a MapLayer and gets upset
when a FeatureSource is not available
(Note this API change is from several releases of GeoTools ago; this is not a
new change).
--
Jody Garnett
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
