Hi, After doing some tests I come to this conclusion.
The goal of the mapper function is the possibility of accessing some styling properties stored in a key<->value structure encoded as a JSON object. Keys are Strings and values are Objects. Values are converted using GeoTools Converters, so they can be of type geometry, string, double, float, etc ... CSS is an interesting approach, although I think is a to "heavy" solution for this use case. Beside, as reference by Pedro the used format needs to be easily parsed by others layers of the architecture. JSON can be easily serialized/deserialized by java, scala, javascript, etc ... and is perfect for REST interfaces. @Aime; I will make a post on geoserver-dev a technical description about the implementation. Best regards, Nuno Oliveira ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
