Chris Holmes wrote:
To make this work right we'd either need FeatureSources to have a
transaction field (that would be used just for the hints), or else
make setTransaction() in FeatureSource.
Either way I feel like using Transaction hints to do rendering stuff
is stretching the design a slight bit too far. Perhaps put hints in
Query itself?
Or do the real solution in the FM branch :-(
Chris the idea is that the render has a "Session" for which it has set
up the hints it needs. The renderer will probably issue several requests
against the same datastore in the same pass.
If we need to add setTransaction to feature source then we can.
Jody
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
