On Fri, Jan 9, 2009 at 7:42 PM, Aaron Kaminsky <aar...@adaptiveplanning.com> wrote:
> My second question has been asked before on this list, but has not been > answered (I think). Why is a given OGNL expression evaluated multiple times > in a single instance? Is there any way to turn that off or work around it? I'm no longer sure what the answer is here. It was added when OGNL was resurrected. I'm not sure if it was a benchmarking thing or used to prime a cache. In any event, I agree that it's quite annoying. I think it was supposed to get fixed, but never did. As far as I know, the issue is on the OGNL side. The workaround is to push whatever you can of your expression into the page class and then use the @Cached annotation from Tacos. -- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
