Hi, Milton Jonathan a écrit : > 2. LineSymbolizerImpl expects a geometry name as a String, while GeoAPI > specifies an Expression. I guess this may go into some big "property > names are/aren't Strings" issue, so I'd like some guidance here: should > we keep using a geometryProperyName as a String in these Impl's, or > should we switch to Expression and have SLD/SEParser pass on a literal > Expression with the geometry name? This has implications on > LineSymbolizerImpl.getGeometryPropertyName, which many people seem to use... > This discution between String/PropertyName/Expression is currently in discussion on the geoapi list and on the JIRA : http://jira.codehaus.org/browse/GEO-159
My opinion is we should have at least a PropertyName to replace the String. But on the other side an Expression is a too vaste and unpredictable object to be used on geometries. johann ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
