Hi all,
I am struggling to understand what is going on with OGNL
compilation/caching in Tapestry 4.1.3.
My first question is regarding the caching of compiled OGNL
expressions. From my reading of the code it looks like the entire
application serializes through the ExpressionCacheImpl.java lock. What
am I missing? Doesn't that mean that if I have an expression that is
very expensive to evaluate that all other hits will be blocked with that
expression is evaluated? Or is that not what the compilation does? Has
anyone else experienced any performance problems that they can trace to
this locking/serialization?
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 have been trying to dig into the source code to figure this out, but I
think I am getting lost in the details. Can someone please explain this
or point me at the information I need?
Thanks and regards,
Aaron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
