You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by ma...@apache.org on 2001/11/04 06:54:51 UTC
cvs commit: jakarta-struts/doc/userGuide building_controller.xml
martinc 01/11/03 21:54:51
Modified: doc/userGuide building_controller.xml
Log:
Roll back one of the changes made for PR 4140, since it was incorrect.
Revision Changes Path
1.8 +0 -6 jakarta-struts/doc/userGuide/building_controller.xml
Index: building_controller.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/building_controller.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- building_controller.xml 2001/11/04 03:07:34 1.7
+++ building_controller.xml 2001/11/04 05:54:50 1.8
@@ -247,12 +247,6 @@
<p>
- For every <form-bean> tag in your <code>struts-config.xml</code>
- file, you must have a corresponding Java class. The same holds true for
- each <action-mapping> tag.
- </p>
-
- <p>
The <code>struts-config.xml</code> file from the example application includes
the following mapping entry for the "log on" function, which we will use
to illustrate the requirements. Note that the entries for all the other actions
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>