Re: [S2] The performance issue about OGNL

On 2/27/07, Shuai Zheng <[EMAIL PROTECTED]> wrote: First of all, when I saw Vlad's email, I copy out the template and delete the original from struts-core.jar. You shouldn't have to delete the one in the JAR. The one under WEB-INF is earlier on the classpath, and it's "first come first served".

Re: [S2] The performance issue about OGNL

This is not a bug per se. The xhtml theme extends the simple theme. If a template doesn't exist in the xhtml theme it will fall back the simple theme. From a performance perspective, you simple need to copy the simple theme hidden.ftl to the xhtml directory. This will allow freemarker to cache

Re: [S2] The performance issue about OGNL

Sorry to disturb again. This issue is because default the s:hidden tag will use xhtml as theme, but actually in the distribution, there is no template/xhtml/hidden.ftl. It always get from template/simple/hidden.ftl. But the cache does not know it. Then this template is recompiled again and again.

Re: [S2] The performance issue about OGNL

One more thing, this only happens on template/xhtml/hidden.ftl. Should I report this as a bug? On 2/27/07, Shuai Zheng <[EMAIL PROTECTED]> wrote: Dear All, Still do research on the debug log and try to get performance improvement, because I try to beat another .net system on speed(it can show

Re: [S2] The performance issue about OGNL

Dear All, Still do research on the debug log and try to get performance improvement, because I try to beat another .net system on speed(it can shows all the pages in 0.5 second,sigh). One more thing I just find out, if the log does not cheat me:) Although I have enabled the property template_up

Re: [S2] The performance issue about OGNL

Dear All, Thanks very much for useful help. Just fight with this for 24 hours and get some improvement. I want to apology first because I am so stupid. Last evening I do a profiling again. The OGNL is not the main bottleneck, but it is still a problem. My previous page loading is around 3-5 se

Re: [S2] The performance issue about OGNL

Ok. I understand. I thought that there was no cache at all. In development, I also need tempalte to be reloaded as soon as possible. But in production, I don't care at all so this si not, for me, a performance issue ... Thanks Mike Vlad2006 a écrit : Hi Mike, As written in the Wiki: "Freem

Re: [S2] The performance issue about OGNL

Hi Mike, As written in the Wiki: "Freemarker fails to properly cache templates when they are retrieved from the classpath. Copying them to the WEB_APP root allows Freemarker to cache them correctly. Freemarker looks at the last modified time of the template to determine if it needs to reload the

Re: [S2] The performance issue about OGNL

There is a page on WebWork Wiki about it: http://wiki.opensymphony.com/display/WW/Performance+Tuning Phil, Since you added this page to the WW wiki, did you also want to add it to the S2 docs? I would suggest putting it in the Configuration section, between Wildcard Mappings and Application Se

Re: [S2] The performance issue about OGNL

>If it is your case, you could make it faster, you have to extract templates >out of webwork.jar (in your case probably struts.jar) and put them in, for >example, WEB-INF/templates directory. Just to know, I saw this many times but without doing this and using only "template_update_delay" in

Re: [S2] The performance issue about OGNL

Hi Zheng, Have you profiled your application? Are you sure it is OGNL that makes your application slow? >From my experience it is not so slow. At least I have not found it too be a bottleneck in my application. Not yet :-). What is really slow in WebWork/Struts2 is jsp tags like, textfield, rad