Jody Garnett wrote:
Corey and I will be updating these interfaces to refer to the latest
publish specification (SLD 1.0), we will also allow for LabelShields,
to ensure that the result is flexable enough to allow for
experimentation.
Well the first idea failed - we need Java 5 type narrowing to pull it off.
The idea was:
- GeoAPI PolygonSymbol - unchanged
- GeoTools PolygonSymbolizer - extend PolygonSymbol
- GeoTools PolygonSymbolizerImpl - implement duplicated method
The obviously has conflicts as the two interfaces report back different
classes for Fill, and Stroke.
Performing the same change on Fill and Stroke is *still* circular,
without Java 5 there is no way for a
GeoTools PolygonSymbolizer to "narrow" the scope and indicate that just
a GeoTools Fill is returned.
So this technique could work, but would break all geoTools renderers and
client code.
Jesse points out that this could be handled with a refactoring tool, but
this is more work then
our short term goal justifies.
This experience will repeat itself Martin, every transition to GeoAPI
interfaces will be
disruptive in nature until we can assume Java 5 as a target.
Jody
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
