Jody Garnett wrote: > The negative feedback was based on intent of the change; which had some > open unresolved issues (we do not know if it is possible with out some > thinking).
Not being standard was cited as one of the reasons against it. Read the mail again. > Sounds like Andrea and I are going to work through that and > either accept the change; or rollback the symbolizer to just be > PropertyName. What we have right now is inconsistent and that does > nobody any good. But now it is a String, so there is nothing to roll back (unless you want to turn that from String to PropertyName). Look in the GeoApi Symbolizer interface: String getGeometryPropertyName(); If we go on with the change that will need to be changed to Expression. Another possible solution is to add a method: Expression getGeometryExpression() only in the GeoTools implementations. Code that is not ready to deal with the new method will just get a null property name, which is valid, and will lead the renderer to use the default geometry. Cheers Andrea ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
