webwork/src/docs/cookbook Performance_Tips.html,1.2,1.3 Reloading_xml_files.html,1.2,1.3 The_Three_Uses_Of_The_Property_Tag.html,1.2,1.3 webwork-blank_app.html,1.1,1.2
[email protected] Mon, 17 Nov 2003 19:08:39 -0800
| Newsgroups | gmane.comp.java.open-symphony.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/opensymphony/webwork/src/docs/cookbook
In directory sc8-pr-cvs1:/tmp/cvs-serv11236
Modified Files:
Performance_Tips.html Reloading_xml_files.html
The_Three_Uses_Of_The_Property_Tag.html webwork-blank_app.html
Log Message:
Refer to 1.4, not 1.3.1
Index: Performance_Tips.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Performance_Tips.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- Performance_Tips.html 15 Nov 2003 03:28:32 -0000 1.2
+++ Performance_Tips.html 18 Nov 2003 03:08:37 -0000 1.3
@@ -1,20 +1,7 @@
<html><head><title>Webwork Performance Tips</title></head><body>
-Here's the place to share your secrets to obtaining blindingly fast WebWork performance.<p class="paragraph"></p>Dick Zetterberg wrote the following on Thu 6 Nov 2003:<p class="paragraph"></p>The discussion and hints below are obsolete and not relevant in the WW1.3 release.
-You might still find the selectfastmap.jsp useful though.<p class="paragraph"></p><hr class="line"></hr><p class="paragraph"></p>Bruce Ritchie Suggested the following on Tue 14 Jan 2003:
-<blockquote class="quote">
-<ul class="minus">
-<li>Use the 1.3 codebase. While it isn't final, it does have some significant improvements like Rickard's FastByteArrayOutputStream for the include tag. That alone is worth it imho.</li>
-<li>There is some areas of improvement that can be made to the codebase that I've found with a profiler. I can't remember all of them off the top of my head, but as an example the search order for action classes in the PrefixActionFactoryProxy class isn't optimal. If you look at the code it will first search for the action in ww's action.standard package then in other packages defined in webwork.properties. This is less then optimal since most action calls (at least in our applications) are not for actions in ww's action package but rather packages we define. This leads to a lot of unneccessary ClassNotFoundExceptions being thrown. A simple solution is to just reverse the search order and search from the end of the prefix list to the front.</li>
-<li>Run the code inside of a profiler such as JProfiler, etc while at the same time hitting the page multiple times (use jmeter or the like). That will easily showcase the hotspots in the code.</blockquote></li>
-</ul><p class="paragraph"></p>Note: These code changes have already been made in CVS for Webwork 1.3.<p class="paragraph"></p>Kirk Rasmussen made the following comment on Tue 14 January 2003:
-<blockquote class="quote">
-After adding the following to my test JSP:
-<div class="wikicode"><pre>java.beans.PropertyEditorManager.registerEditor(<span class="java-object">String</span>.class, sun.beans.editors.StringEditor.class);</pre></div><p class="paragraph"></p>I got a significant boost in performance but its still a little slow.
-<ol>
-<li><ui:select> tag: Execution Time=4.253 sec</li>
-<li><ui:iterator> with <ui:property> tag: Execution Time=0.449 sec</li>
-<li>JSP scriptlet using WW API: Execution Time=0.0020 sec</li>
-</ol><p class="paragraph"></p>At this point I'm thinking of just implementing it as an include as a JSP scriplet using the WW API for the country list.</blockquote><p class="paragraph"></p>See the commentas for another tip for using property editors.<p class="paragraph"></p>Peter Kelley (me) made the following comment (somewhat reformatted) on Thu 23 January 2003:
+Here's the place to share your secrets to obtaining blindingly fast WebWork performance.<p class="paragraph"></p>Not that the discussion and hints below are obsolete and not relevant in the WW1.4 release.
+You might still find the selectfastmap.jsp useful though.<p class="paragraph"></p><hr class="line"></hr>
+Peter Kelley made the following comment (somewhat reformatted) on Thu 23 January 2003:
<blockquote class="quote">
OK I've been doing some numbers on performance and I thought I'd share
my results with the list.
@@ -121,4 +108,4 @@
}
%>
</select>
-<%@ include file=<span class="java-quote">"controlfooter.jsp"</span> %></pre></div><p class="paragraph"></p></body></html>
\ No newline at end of file
+<%@ include file=<span class="java-quote">"controlfooter.jsp"</span> %></pre></div></body></html>
\ No newline at end of file
Index: Reloading_xml_files.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Reloading_xml_files.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- Reloading_xml_files.html 15 Nov 2003 03:28:32 -0000 1.2
+++ Reloading_xml_files.html 18 Nov 2003 03:08:37 -0000 1.3
@@ -1,2 +1,2 @@
<html><head><title>Reloading xml files</title></head><body>
-Webwork 1.3.1 allows for dynamic reloading of xml configuration file (ie, reloading actions.xml).<p class="paragraph"></p>In order to enable this feature, add the following to your webwork.properties file:<p class="paragraph"></p><div class="wikicode"><pre>webwork.configuration.xml.reload=<span class="java-keyword">true</span></pre></div><p class="paragraph"></p></body></html>
\ No newline at end of file
+Webwork 1.4 allows for dynamic reloading of xml configuration file (ie, reloading actions.xml).<p class="paragraph"></p>In order to enable this feature, add the following to your webwork.properties file:<p class="paragraph"></p><div class="wikicode"><pre>webwork.configuration.xml.reload=<span class="java-keyword">true</span></pre></div></body></html>
\ No newline at end of file
Index: The_Three_Uses_Of_The_Property_Tag.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/The_Three_Uses_Of_The_Property_Tag.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- The_Three_Uses_Of_The_Property_Tag.html 15 Nov 2003 03:28:32 -0000 1.2
+++ The_Three_Uses_Of_The_Property_Tag.html 18 Nov 2003 03:08:37 -0000 1.3
@@ -14,7 +14,7 @@
escaped by default. You can override this with explicit setting of the escape attribute.
Quoted text that is escaped will have its outer quotes stripped.<p class="paragraph"></p>If id is specified, it will use the third use case.
<div class="wikicode"><pre><webwork:property id=<span class="java-quote">"foo"</span> value=<span class="java-quote">"bar"</span> /></pre></div>
-will grab the value "bar" from the value stack and put it into the page context as "foo". It will be added both to the page scope and to the request scope. Note that webwork 1.3.1 introduces a new push tag that achieves this functionality too, for the sake of clarity.<p class="paragraph"></p>Here are some more examples of fun to be had:<p class="paragraph"></p><div class="wikicode"><pre><ww:property value=<span class="java-quote">"x/y"</span>></pre></div> will print getX().getY()<p class="paragraph"></p><div class="wikicode"><pre><ww:property /></pre></div> will print what's on the top of the stack. This is very useful to debug where you are on the stack - and often will print out the toString() method of your action.
+will grab the value "bar" from the value stack and put it into the page context as "foo". It will be added both to the page scope and to the request scope. Note that webwork 1.4 introduces a new push tag that achieves this functionality too, for the sake of clarity.<p class="paragraph"></p>Here are some more examples of fun to be had:<p class="paragraph"></p><div class="wikicode"><pre><ww:property value=<span class="java-quote">"x/y"</span>></pre></div> will print getX().getY()<p class="paragraph"></p><div class="wikicode"><pre><ww:property /></pre></div> will print what's on the top of the stack. This is very useful to debug where you are on the stack - and often will print out the toString() method of your action.
<h3 class="heading-1">So why is the second use case useful?
</h3><p class="paragraph"></p>It makes your code simpler and easier to read!<p class="paragraph"></p><div class="wikicode"><pre><ww:property value=<span class="java-quote">"someUser"</span>>
<ww:property value=<span class="java-quote">"name"</span> />
<ww:property value=<span class="java-quote">"fullName"</span> />
Index: webwork-blank_app.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/webwork-blank_app.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- webwork-blank_app.html 11 Nov 2003 18:34:46 -0000 1.1
+++ webwork-blank_app.html 18 Nov 2003 03:08:37 -0000 1.2
@@ -1,2 +1,2 @@
<html><head><title>webwork-blank app</title></head><body>
-Webwork 1.3.1 comes with an updated skeleton application zip. Simply unpack this, run ant using the included build file, and point your servlet container at the skeleton application's directory and you will have a webwork app up and running.</body></html>
\ No newline at end of file
+Webwork 1.4 comes with an updated skeleton application zip. Simply unpack this, run ant using the included build file, and point your servlet container at the skeleton application's directory and you will have a webwork app up and running.</body></html>
\ No newline at end of file
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl