Jody Garnett ha scritto:
> Interesting.
>
> Could you add some kind of scoping? Something like ${feature.bounds} for the
> bounds of the current feature?
How has that anything to do with the topic of this thread? :-)
The environment function has no feature scoping, the values are
set using setLocalValues and setGlobalValues (and equivalent
single key methods).
If you want to access feature properties you use a PropertyName no?
Maybe you're wondering how the value in the env function maps
can change? Three examples:
- a second thread that messes with the global map while the
rendering is going
- a rendering listener (acting thus in the same thread) that changes
the values in the env function maps
- another filter function that calls into EnvFunction.setLocalValues()
as rendering goes, maybe as an attempt to become stateful for
the length of the rendering
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
