Doesn't <s:head...> have a parseContent attribute? Either way, you may just be able to replicate the <s:head...> generated code with your own.
Dave --- On Mon, 6/9/08, Richard Sayre <[EMAIL PROTECTED]> wrote: > From: Richard Sayre <[EMAIL PROTECTED]> > Subject: Re: Struts 2 Performance > To: "Struts Users Mailing List" <user@struts.apache.org> > Date: Monday, June 9, 2008, 10:53 AM > Thank you for the dojo info. I did a custom build for dojo > using > http://cwiki.apache.org/confluence/display/S2WIKI/Creating+a+custom+Dojo+profile+for+Struts+2.0.x > and it reduced alot of requests > > I would like to turn off the page scan that dojo does and > add the > bootstrap code for the widgits my self. I'm not sure > what to search > for to find information on this. Can you point me to any > articles or > documentation? > > Thank you, > > Rich > > > On Fri, May 30, 2008 at 5:05 PM, Laurie Harper > <[EMAIL PROTECTED]> wrote: > > Richard Sayre wrote: > >> > >> Hi, > >> > >> I have a few questions regarding performance in > Struts 2. > >> > >> First of all we are using 2.0.9. I am trying to > get the source to fix > >> the following memory leaks : > >> https://issues.apache.org/struts/browse/WW-2167 > but I can't find the > >> 2.0.9 build. Can anyone point me to the source > for that build? > > > > > http://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_2_0_9/ > > > >> We have several Struts 2 applications hosted on a > Tomcat server. We > >> have a copy of our Struts libraries in each of the > applications > >> WEB-INF folder. Is there a better way to have > this set up to save > >> memory? I know this is more of a tomcat question > but I figured some > >> one here might have some suggestions. > > > > As Giovanni said, you can put the struts jars (and > dependencies) into a > > shared lib folder. You don't need to introduce > Tomcat instancing to do this, > > though. I should also point out that this isn't a > tested configuration, so > > you will want to test thoroughly. > > > >> Also, when I run Firebug to check the loading time > of my page it seems > >> that alot of time is spent downloading Dojo > scripts. I am only using > >> the Ajax and the Tabbed Panel provided by dojo, > nothing else. Is > >> there a way to configure dojo to only use what is > nessessary? I did > >> see a post on this list a while ago that involved > extracting the files > >> and rewriting the dojo require file, is this > still the best way to > >> increase dojo performance? > > > > Yes; you can improve the Dojo multiple-http-requests > issue by creating a > > custom Dojo build, which will bundle everything you > use into dojo.js. You > > will then see only one request (for dojo.js) in place > of the multiple > > requests you have now. See the Dojo documentation for > how to create a custom > > profile/build, or see below. > > > >> I was also getting a "script is busy - cancel > or continue" in IE and > >> Firefox. This was on a page that has a alot of > HTML divs. I finally > >> narrowed it down to some dojo that was running > that seemed to be > >> looping through every element on the page after it > loaded. Does > >> anyone have any insight into this behavior? Why > is it needed? > > > > By default, Dojo scans the entire page looking for > widgets to instantiate > > (i.e. looking for tags with a dojoType attribute). For > pages with a lot of > > markup, that can be quite costly. There's a Dojo > configuration switch to > > turn that off, but then you need to add code to > bootstrap the widgets. > > > >> Does the latest version 2.0.11.1 use a different > version of dojo? > >> Does it perform better? Would there be alot of > code changes to change > >> from 0.4 to the version that the current build > uses? > > > > 2.0.11.1 doesn't offer much improvement, but 2.1.2 > (beta) does. 2.1.2 comes > > with a custom Dojo build pre-baked and with widget > scanning turned off (it > > also handles the widget bootstrapping for you). > It's certainly more work to > > upgrade to 2.1.2 than 2.0.11.1 but, given your > concerns, it is probably > > worth it. > > > > L. > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
