webwork/src/docs/cookbook Action_Aliasing.html,1.1,1.2 Action_Tag.html,1.1,1.2 CookBook.html,1.2,1.3 Form_Validation.html,1.1,1.2 Handling_file_uploads.html,1.1,1.2 How_to_add_retrieve_from_HttpSession.html,1.1,1.2 How_to_return_a_view_with_zero_code.html,1.1,1.2 Iterating_Different_Objects.html,1.1,1.2 Iterating_over_a_Map.html,1.1,1.2 Multiple_Graphical_Submit_Buttons.html,1.1,1.2 Performance_Tips.html,1.1,1.2 Populate_Form_Bean_and_access_its_value.html,1.1,1.2 Prepared_Actions.html,1.1,1.2 Reloading_Java_Actions.html,1.1,1.2 Reloading_xml_files.html,1.1,1.2 Rules_of_the_Value_Stack.html,1.1,1.2 Running_WebWork_on_SunONE.html,1.1,1.2 Select_Tag_Tips.html,1.1,1.2 SessionAware_Actions.html,1.1,1.2 Skinning.html,1.1,1.2 The_Three_Uses_Of_The_Property_Tag.html,1.1,1.2 Using_CommandDriven_Actions.html,1.1,1.2 Using_JSTL_seamlessly_with_WebWork.html,1.1,1.2 Using_WebWork_Components.html,1.1,1.2
[email protected] Fri, 14 Nov 2003 19:28:35 -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-serv13777
Modified Files:
Action_Aliasing.html Action_Tag.html CookBook.html
Form_Validation.html Handling_file_uploads.html
How_to_add_retrieve_from_HttpSession.html
How_to_return_a_view_with_zero_code.html
Iterating_Different_Objects.html Iterating_over_a_Map.html
Multiple_Graphical_Submit_Buttons.html Performance_Tips.html
Populate_Form_Bean_and_access_its_value.html
Prepared_Actions.html Reloading_Java_Actions.html
Reloading_xml_files.html Rules_of_the_Value_Stack.html
Running_WebWork_on_SunONE.html Select_Tag_Tips.html
SessionAware_Actions.html Skinning.html
The_Three_Uses_Of_The_Property_Tag.html
Using_CommandDriven_Actions.html
Using_JSTL_seamlessly_with_WebWork.html
Using_WebWork_Components.html
Log Message:
Bugfix in scraper, get rid of unmatched end </div>
Index: Action_Aliasing.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Action_Aliasing.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Action_Aliasing.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Action_Aliasing.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -5,5 +5,4 @@
ChangeCarPrice.success=showcar.jsp<p class="paragraph"></p>AdjustFoodPrice.action=SelectFood
AdjustFoodPrice.success=ChangeFoodPrice.action
ChangeFoodPrice.action=AdjustPrice
-ChangeFoodPrice.success=showfood.jsp</pre></div>
-</div></body></html>
\ No newline at end of file
+ChangeFoodPrice.success=showfood.jsp</pre></div></body></html>
\ No newline at end of file
Index: Action_Tag.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Action_Tag.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Action_Tag.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Action_Tag.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -5,6 +5,4 @@
<ww:param name=<span class="java-quote">"user"</span>>username</ww:param>
<ww:property name=<span class="java-quote">"firstName"</span>/>
<ww:property name="lastName />
-</ww:action></pre></div>
-
-</div></body></html>
\ No newline at end of file
+</ww:action></pre></div></body></html>
\ No newline at end of file
Index: CookBook.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/CookBook.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- CookBook.html 13 Nov 2003 04:21:51 -0000 1.2
+++ CookBook.html 15 Nov 2003 03:28:32 -0000 1.3
@@ -25,5 +25,4 @@
<li><a href="Using_JSTL_seamlessly_with_WebWork.html">Using JSTL seamlessly with WebWork</a></li>
<li><a href="Handling_file_uploads.html">Handling file uploads</a></li>
<li><a href="Using_WebWork_Components.html">Using WebWork Components</a> (Webwork 2 only)</li>
-</ul>
-</div></body></html>
\ No newline at end of file
+</ul></body></html>
\ No newline at end of file
Index: Form_Validation.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Form_Validation.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Form_Validation.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Form_Validation.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -15,6 +15,4 @@
}</pre></div><p class="paragraph"></p>The length check will only happen on a form POST operation that contains the "password" parameter. If you directly access the action with a GET, the length check will not happen because the password parameter will be missing from the request.<p class="paragraph"></p>It is probably better to make that check from the doValidation() method of the Action object in this case. The PropertyEditor validation is best used when a value is actually set.<p class="paragraph"></p>Another issue to consider is when using the "PrepareAction" marker interface. If you set the value directly in the prepare() method of your action object then the PropertyEditor validation will not happen either. You should call BeanUtil.setProperty() within prepare() if you want your validation rules to apply.<p class="paragraph"></p><div class="wikicode"><pre><span class="java-keyword">public</span> void prepare()
{
webwork.util.BeanUtil.setProperty(<span class="java-quote">"password"</span>, <span class="java-quote">"test"</span>, <span class="java-keyword">this</span>);
- }</pre></div>
-
-</div></body></html>
\ No newline at end of file
+ }</pre></div></body></html>
\ No newline at end of file
Index: Handling_file_uploads.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Handling_file_uploads.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Handling_file_uploads.html 13 Nov 2003 04:21:51 -0000 1.1
+++ Handling_file_uploads.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -47,5 +47,4 @@
<span class="java-keyword">if</span> (file == <span class="java-keyword">null</span>) {
addActionError(<span class="java-quote">"Error uploading: "</span> + multiWrapper.getFilesystemName(inputValue));
}<p class="paragraph"></p> // Do additional processing/logging...
-}</pre></div>
-</div></body></html>
\ No newline at end of file
+}</pre></div></body></html>
\ No newline at end of file
Index: How_to_add_retrieve_from_HttpSession.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/How_to_add_retrieve_from_HttpSession.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- How_to_add_retrieve_from_HttpSession.html 11 Nov 2003 18:34:46 -0000 1.1
+++ How_to_add_retrieve_from_HttpSession.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -19,6 +19,4 @@
<div class="wikicode"><pre><%@ taglib uri=<span class="java-quote">"webwork"</span> prefix=<span class="java-quote">"ww"</span> %>
<html>
<ww:property value=<span class="java-quote">"@name/toUpperCase"</span> />
-</html></pre></div>
-
-</div></body></html>
\ No newline at end of file
+</html></pre></div></body></html>
\ No newline at end of file
Index: How_to_return_a_view_with_zero_code.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/How_to_return_a_view_with_zero_code.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- How_to_return_a_view_with_zero_code.html 11 Nov 2003 18:34:46 -0000 1.1
+++ How_to_return_a_view_with_zero_code.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -1,5 +1,4 @@
<html><head><title>How to return a view with zero code</title></head><body>
So you want to return a view say an index.jsp and you dont want people to just hit the file, or you have a view but dont have any model or processing to do yet and you want to prototype,but through webwork, this is for you.<p class="paragraph"></p>There isn't much to it really, as part of the core webwork library there is a class called webwork.action.ActionSupport.<p class="paragraph"></p>This class is basically there for extension but we can use it here because it implements enough functionality namely doExecute among other stuff,and returns SUCCESS which is all we need.<p class="paragraph"></p>In views.properties you do something like this:
<div class="wikicode"><pre>test.action=webwork.action.ActionSupport
-test.success=test.jsp</pre></div><p class="paragraph"></p>Then you too can hit your view through webwork with zero code.
-</div></body></html>
\ No newline at end of file
+test.success=test.jsp</pre></div><p class="paragraph"></p>Then you too can hit your view through webwork with zero code.</body></html>
\ No newline at end of file
Index: Iterating_Different_Objects.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Iterating_Different_Objects.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Iterating_Different_Objects.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Iterating_Different_Objects.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -18,5 +18,4 @@
<webwork:property value=<span class="java-quote">"name"</span>>
</webwork:<span class="java-keyword">else</span>>
<br>
-</webwork:iterator></pre></div><p class="paragraph"></p>This will now print any 'iteratable' object (array, list, collection, XML node list, vector, enumeration iterator, map values, etc) containing any objects with a getName() method.<p class="paragraph"></p>Note that those getName() methods could return String or any Object that is printable! WebWork will call the toString() method when printing an object if it is not a String.<p class="paragraph"></p>Also note that in the WebWork expression language test="id" is not the same as test="id == true". test="id" is testing that id exists and is not null. Here our Baz object has not getId() method hence the if test will fail.<p class="paragraph"></p>This functionality is available across all of WebWork's iteration tags, and not just the iterator tag.<p class="paragraph"></p>For the sake of focussing on one issue at a time, the examples above specify url's via <a href>, it is of course far preferable to use the we
bwork url tag that will allow for much cleaner specification of parameters and suchlike.
-</div></body></html>
\ No newline at end of file
+</webwork:iterator></pre></div><p class="paragraph"></p>This will now print any 'iteratable' object (array, list, collection, XML node list, vector, enumeration iterator, map values, etc) containing any objects with a getName() method.<p class="paragraph"></p>Note that those getName() methods could return String or any Object that is printable! WebWork will call the toString() method when printing an object if it is not a String.<p class="paragraph"></p>Also note that in the WebWork expression language test="id" is not the same as test="id == true". test="id" is testing that id exists and is not null. Here our Baz object has not getId() method hence the if test will fail.<p class="paragraph"></p>This functionality is available across all of WebWork's iteration tags, and not just the iterator tag.<p class="paragraph"></p>For the sake of focussing on one issue at a time, the examples above specify url's via <a href>, it is of course far preferable to use the we
bwork url tag that will allow for much cleaner specification of parameters and suchlike.</body></html>
\ No newline at end of file
Index: Iterating_over_a_Map.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Iterating_over_a_Map.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Iterating_over_a_Map.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Iterating_over_a_Map.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -6,5 +6,4 @@
key= $entry.key, value=$entry.value<br>
#end</pre></div><p class="paragraph"></p>To iterate over the error map in a JSP:<p class="paragraph"></p><div class="wikicode"><pre><ww:iterator value=<span class="java-quote">"errors"</span>>
key=<ww:property value=<span class="java-quote">"key"</span>/>, value=<ww:property value=<span class="java-quote">"value"</span>/><br>
-</ww:iterator></pre></div>
-</div></body></html>
\ No newline at end of file
+</ww:iterator></pre></div></body></html>
\ No newline at end of file
Index: Multiple_Graphical_Submit_Buttons.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Multiple_Graphical_Submit_Buttons.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Multiple_Graphical_Submit_Buttons.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Multiple_Graphical_Submit_Buttons.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -19,5 +19,4 @@
setDoUpdate( <span class="java-quote">"<span class="java-keyword">true</span>"</span> );
}
}
-}</pre></div>
-</div></body></html>
\ No newline at end of file
+}</pre></div></body></html>
\ No newline at end of file
Index: Performance_Tips.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Performance_Tips.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Performance_Tips.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Performance_Tips.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -121,5 +121,4 @@
}
%>
</select>
-<%@ include file=<span class="java-quote">"controlfooter.jsp"</span> %></pre></div><p class="paragraph"></p>
-</div></body></html>
\ No newline at end of file
+<%@ include file=<span class="java-quote">"controlfooter.jsp"</span> %></pre></div><p class="paragraph"></p></body></html>
\ No newline at end of file
Index: Populate_Form_Bean_and_access_its_value.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Populate_Form_Bean_and_access_its_value.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Populate_Form_Bean_and_access_its_value.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Populate_Form_Bean_and_access_its_value.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -18,5 +18,4 @@
</webwork:property></pre></div>
This is a good way to do it if you have several parameters from the TestBean that you want to display, but, if you have just one, like in this case, it's probably better to do this:
<div class="wikicode"><pre><webwork:property value=<span class="java-quote">"myBean/name"</span>/></pre></div>
-Which will call getMyBean.getName() and print that out to the page.
-</div></body></html>
\ No newline at end of file
+Which will call getMyBean.getName() and print that out to the page.</body></html>
\ No newline at end of file
Index: Prepared_Actions.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Prepared_Actions.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Prepared_Actions.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Prepared_Actions.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -1,4 +1,3 @@
<html><head><title>Prepared Actions</title></head><body>
If your action implements PrepareAction, before any set methods are called,prepare() will run. In the prepare method you do whatever pre-processing you might have, say get some records from a database.<p class="paragraph"></p>Consult the API documentation for PrepareAction for more information.<p class="paragraph"></p><div class="wikicode"><pre><span class="java-keyword">public</span> <span class="java-keyword">interface</span> PrepareAction</pre></div><p class="paragraph"></p>An Action that needs to prepare its state before receiving parameters should implement this interface. A common use is to get current state from a database, which then is overwritten partially by input parameters. The new state, including the old that was not overwritten, may then be sent back to the database<p class="paragraph"></p><div class="wikicode"><pre><span class="java-keyword">public</span> void prepare() <span class="java-keyword">throws</span> java.lang.Exception</pre></div><
p class="paragraph"></p> This method is called to allow the action to prepare itself before receiving parameters through its set-methods.All *Aware interfaces are checked before this, so the action can rely on addition information to have been sent through the callbacks (e.g. the application session, or user session)<p class="paragraph"></p><div class="wikicode"><pre>Throws:
-java.lang.Exception - thrown if a system level exception occurs.</pre></div>
-</div></body></html>
\ No newline at end of file
+java.lang.Exception - thrown if a system level exception occurs.</pre></div></body></html>
\ No newline at end of file
Index: Reloading_Java_Actions.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Reloading_Java_Actions.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Reloading_Java_Actions.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Reloading_Java_Actions.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -3,5 +3,4 @@
<h3 class="heading-1">2 Rationale
</h3><p class="paragraph"></p>The rationale for this is that while most appservers provide for hot redeployment of webapps, it is often a fairly slow process. This is especially the case if you have a lot of data in your sessions, or have a startup listener which initializes caches, starts off a scheduler, or performs other time consuming startup tasks. Containers that do detect class file changes will go through all that startup expense since they will reload the entire application.<p class="paragraph"></p>Webwork actions lend themselves to easy reloading since they are never reused, and a new action is instantiated every time for a given request. This means that they do not hang around and nothing should be holding onto them. Dropping in an updated class file therefore is very easy and quick.
<h3 class="heading-1">3 Caveats
</h3><p class="paragraph"></p>There are also downsides to this approach. Chief amongst these is the fact that a custom classloader is not allowed by the servlet spec. Secondly, there is a (fairly slight) performance hit when using this flag. However, this should not be much of a problem since this setting is aimed at a development environment only, and is not to be used in a live deployment. By default, action reloading is not enabled.
<h3 class="heading-1">4 Usage
</h3><p class="paragraph"></p>Add the following configuration setting to your <b class="bold">webwork.properties</b> file:
-<div class="wikicode"><pre>webwork.action.java.reload=<span class="java-keyword">true</span></pre></div>
-</div></body></html>
\ No newline at end of file
+<div class="wikicode"><pre>webwork.action.java.reload=<span class="java-keyword">true</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.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Reloading_xml_files.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Reloading_xml_files.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -1,3 +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>
-</div></body></html>
\ No newline at end of file
+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
Index: Rules_of_the_Value_Stack.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Rules_of_the_Value_Stack.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Rules_of_the_Value_Stack.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Rules_of_the_Value_Stack.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -8,5 +8,4 @@
</ol>
<ul class="star">
<li>The ValueStack is only valid during one request / response cycle.</li>
-</ul><p class="paragraph"></p>How is that for a brief primer? Anyone have any other rules to add?
-</div></body></html>
\ No newline at end of file
+</ul><p class="paragraph"></p>How is that for a brief primer? Anyone have any other rules to add?</body></html>
\ No newline at end of file
Index: Running_WebWork_on_SunONE.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Running_WebWork_on_SunONE.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Running_WebWork_on_SunONE.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Running_WebWork_on_SunONE.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -3,6 +3,4 @@
<ol>
<li>Give Write Permissions to java.util.PropertyPermission.</li>
<li>Add java.lang.reflect.ReflectPermission "suppressAccessChecks"</li>
-</ol>
-
-</div></body></html>
\ No newline at end of file
+</ol></body></html>
\ No newline at end of file
Index: Select_Tag_Tips.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Select_Tag_Tips.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Select_Tag_Tips.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Select_Tag_Tips.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -1,5 +1,4 @@
<html><head><title>Select Tag Tips</title></head><body>
ever happen to have a List of Maps that you would like to render as a select tag in html?<p class="paragraph"></p>just make sure your action returns a List of Maps<p class="paragraph"></p>
heres how to do it:<p class="paragraph"></p><div class="wikicode"><pre><ui:select label=<span class="java-quote">"'Category'"</span> name=<span class="java-quote">"'categoryId'"</span> list=<span class="java-quote">"categorys"</span>
-listKey=<span class="java-quote">"'['id']'"</span> listValue=<span class="java-quote">"'['name']'"</span>/></pre></div><p class="paragraph"></p><br></br><p class="paragraph"></p>what about one huge Map?<p class="paragraph"></p><div class="wikicode"><pre><ui:select label=<span class="java-quote">"'State'"</span> name=<span class="java-quote">"'stateId'"</span> list=<span class="java-quote">"states/keySet"</span> listKey=<span class="java-quote">"'.'"</span> listValue=<span class="java-quote">"'states[.]'"</span>/></pre></div>
-</div></body></html>
\ No newline at end of file
+listKey=<span class="java-quote">"'['id']'"</span> listValue=<span class="java-quote">"'['name']'"</span>/></pre></div><p class="paragraph"></p><br></br><p class="paragraph"></p>what about one huge Map?<p class="paragraph"></p><div class="wikicode"><pre><ui:select label=<span class="java-quote">"'State'"</span> name=<span class="java-quote">"'stateId'"</span> list=<span class="java-quote">"states/keySet"</span> listKey=<span class="java-quote">"'.'"</span> listValue=<span class="java-quote">"'states[.]'"</span>/></pre></div></body></html>
\ No newline at end of file
Index: SessionAware_Actions.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/SessionAware_Actions.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- SessionAware_Actions.html 11 Nov 2003 18:34:46 -0000 1.1
+++ SessionAware_Actions.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -5,5 +5,4 @@
session=m;
}
// extra code follows…
-}</pre></div><p class="paragraph"></p>The session data will now be available via the session variable. Calling session.clear() will magically invalidate the servlet session (if, of course, this <b class="bold">is</b> a servlet session).
-</div></body></html>
\ No newline at end of file
+}</pre></div><p class="paragraph"></p>The session data will now be available via the session variable. Calling session.clear() will magically invalidate the servlet session (if, of course, this <b class="bold">is</b> a servlet session).</body></html>
\ No newline at end of file
Index: Skinning.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Skinning.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Skinning.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Skinning.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -1,5 +1,4 @@
<html><head><title>Skinning</title></head><body>
A very usable feature of webwork actions is that they are location independant. This means that <span class="nobr"></img><a href="http://yourdomain.com/Foo.action">http://yourdomain.com/Foo.action</a></span> will execute the same action as <span class="nobr"></img><a href="http://yourdomain.com/bar/Foo.action.">http://yourdomain.com/bar/Foo.action.</a></span> The views you have mapped in your views.properties (or views.xml) are paths relative to where you executed the action (/ and /bar in the examples above). This feature can be used for skinning with a simple views.properties file like this: <div class="wikicode"><pre>Foo.success=foo.jsp
Foo.error=foo-error.jsp</pre></div>
-Now in your web application you might want to have two different views for HTML and WML clients. Simply put a file called foo.jsp that outputs HTML in a folder called (for simplicities sake) "html" and another foo.jsp that outputs WML in a folder called "wml". Then all you have to do to access the html version is use the address <span class="nobr"></img><a href="http://yourdomain.com/html/Foo.action">http://yourdomain.com/html/Foo.action</a></span> and to use the WML version do <span class="nobr"></img><a href="http://yourdomain.com/wml/Foo.action.">http://yourdomain.com/wml/Foo.action.</a></span><p class="paragraph"></p>This method is good for skinning, supporting different browsers (you might want simpler layout for a PDA for example) and so forth.<p class="paragraph"></p>Since the request path is /wml and the view page specified was relative, the acual view page that will be used will actually be /wml/foo.jsp.
-</div></body></html>
\ No newline at end of file
+Now in your web application you might want to have two different views for HTML and WML clients. Simply put a file called foo.jsp that outputs HTML in a folder called (for simplicities sake) "html" and another foo.jsp that outputs WML in a folder called "wml". Then all you have to do to access the html version is use the address <span class="nobr"></img><a href="http://yourdomain.com/html/Foo.action">http://yourdomain.com/html/Foo.action</a></span> and to use the WML version do <span class="nobr"></img><a href="http://yourdomain.com/wml/Foo.action.">http://yourdomain.com/wml/Foo.action.</a></span><p class="paragraph"></p>This method is good for skinning, supporting different browsers (you might want simpler layout for a PDA for example) and so forth.<p class="paragraph"></p>Since the request path is /wml and the view page specified was relative, the acual view page that will be used will actually be /wml/foo.jsp.</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.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- The_Three_Uses_Of_The_Property_Tag.html 11 Nov 2003 18:34:46 -0000 1.1
+++ The_Three_Uses_Of_The_Property_Tag.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -24,5 +24,4 @@
<ww:property value=<span class="java-quote">"someUser/email"</span> /></pre></div><p class="paragraph"></p>Potentially slower? Yes - because the first code snippet only calls getSomeUser() once - whereas the second makes 3 calls to getSomeUser() - so your user lookup might be done 3 times.<p class="paragraph"></p>You can also use the .. operator to refer back to other things if you wanted to like so:<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">"../score(.)"</span> />
-</ww:property></pre></div><p class="paragraph"></p>The "../score(.)" will call yourAction.getScore(someUser) where someUser is the object obtained from getSomeUser().
-</div></body></html>
\ No newline at end of file
+</ww:property></pre></div><p class="paragraph"></p>The "../score(.)" will call yourAction.getScore(someUser) where someUser is the object obtained from getSomeUser().</body></html>
\ No newline at end of file
Index: Using_CommandDriven_Actions.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Using_CommandDriven_Actions.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Using_CommandDriven_Actions.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Using_CommandDriven_Actions.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -19,5 +19,4 @@
for "greet.goodbye" --- it's got "!goodbye" appended to the Action's
class name. This declares that instead of performing the default
action, which is doExecute(), when this alias is hit the doGoodbye
-method should be used instead.<p class="paragraph"></p>Note that the do* method should be public, return a String and have no parameters or it won't be found.<p class="paragraph"></p>Why is this useful? Well, it's simply an alternative way of going about certain things. Let's say for example you have a set of pages that perform CRUD (create, read, update, delete) operations on some object. One possible way to implement this would be to have one base action class that deals with looking up the object and other such 'common' functionality, with subclasses for each of the CRUD operations. Alternatively, you could use commands, with one action class defining doUpdate(), doDelete(), doCreate(), with the doExecute perhaps handling the read view.<p class="paragraph"></p>Finally, it is important to note that validation is NOT called automatically for command methods. If you need validation then you should call doValidate() explicitly within your commands.
-</div></body></html>
\ No newline at end of file
+method should be used instead.<p class="paragraph"></p>Note that the do* method should be public, return a String and have no parameters or it won't be found.<p class="paragraph"></p>Why is this useful? Well, it's simply an alternative way of going about certain things. Let's say for example you have a set of pages that perform CRUD (create, read, update, delete) operations on some object. One possible way to implement this would be to have one base action class that deals with looking up the object and other such 'common' functionality, with subclasses for each of the CRUD operations. Alternatively, you could use commands, with one action class defining doUpdate(), doDelete(), doCreate(), with the doExecute perhaps handling the read view.<p class="paragraph"></p>Finally, it is important to note that validation is NOT called automatically for command methods. If you need validation then you should call doValidate() explicitly within your commands.</body></html>
\ No newline at end of file
Index: Using_JSTL_seamlessly_with_WebWork.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Using_JSTL_seamlessly_with_WebWork.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Using_JSTL_seamlessly_with_WebWork.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Using_JSTL_seamlessly_with_WebWork.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -82,5 +82,4 @@
</filter-mapping><p class="paragraph"></p><filter-mapping>
<filter-name>jstlfilter</filter-name>
<url-pattern>*.action</url-pattern>
-</filter-mapping></pre></div>
-</div></body></html>
\ No newline at end of file
+</filter-mapping></pre></div></body></html>
\ No newline at end of file
Index: Using_WebWork_Components.html
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/docs/cookbook/Using_WebWork_Components.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Using_WebWork_Components.html 11 Nov 2003 18:34:46 -0000 1.1
+++ Using_WebWork_Components.html 15 Nov 2003 03:28:32 -0000 1.2
@@ -10,6 +10,4 @@
<param name=<span class="java-quote">"location"</span>>/success.jsp</param>
</result>
<interceptor-ref name=<span class="java-quote">"defaultComponentStack"</span>/>
-</action></pre></div><p class="paragraph"></p>WebWork will call the interface and set the Counter bean . The Counter bean would then be subsequently be available to be used by your *Action classes.<p class="paragraph"></p>
-
-</div></body></html>
\ No newline at end of file
+</action></pre></div><p class="paragraph"></p>WebWork will call the interface and set the Counter bean . The Counter bean would then be subsequently be available to be used by your *Action classes.<p class="paragraph"></p></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