Hi Kaspar, you are right OGNL bytecode compilation is enabled in all Tapestry-versions >= 4.1.2. As far as I can see, the performance improvements will be substantial for high-volume public sites where server-cpu load is a performance-bottleneck. If you are not satisfied with rendering times in single-/few user tests, I'd think of db-roundtrips rather than OGNL as the usual suspect. After all, only performance profiling will really tell (see YourKit, for example).
--Marcus 2007/12/20, Kaspar Fischer <[EMAIL PROTECTED]>: > > Dear list, > > I am confused about the status of OGNL that comes with Tapestry 4.1.3. > I read on > > http://blog.opencomponentry.com/2007/01/14/new-ognl-release-on-the- > horizon-its-faster > > that bytecode compilation has been implemented for OGNL and that this > is in Tapestry 4.1.2 already. > > * Is this the case? > > * Do I have to enable OGNL bytecode compilation in some way? > (We have quite high rendering times and I wonder whether OGNL is > resonsible.) > > * Does this mean that tapestry-prop, > > http://howardlewisship.com/tapestry-javaforge/tapestry-prop/ > > which you cannot download currently, is not needed anymore? > > Thanks, > Kaspar > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Marcus Schulte http://marcus-schulte.blogspot.com
