Jody Garnett ha scritto: > Justin Deoliveira wrote: >> 1. By not processing the extension point, and not picking up the slow >> xpath processing property accessor. Instantiate a fast processor and >> just use it. > You would need to look at the expression and confirm that xpath was not > used. You are performing the check once - prior to rendering. The check > should be an easy implementation of StyleVisistor+FilterVisitor - indeed > this may already be done in order to check if any non geometry > attributes are needed as part of the query. >> 2. Use the hinting system to specify that you want to use the fast >> property accessor. Not sure the expression api allows us to pull this >> one off. > This amounts to the same thing; you would need to perform the check in > order to determine that the hint should be applied. > > Andrea can a lazy approach be tried? That is the first time the Filter > is executed it can find the correct property accessor; subsequent run's > can start off by assuming the property accessor will work. Reading ahead > in your email it sounds like this is the approach you have taken?
Sure, but I have no time to put on this. Versioning WFS has been delayed due to 1.5.x release and trunk merge, now I have to work on it full steam. Cheers Andrea ------------------------------------------------------------------------- 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
