cedric 2003/07/21 08:23:34
Modified: web/tiles-documentation/WEB-INF struts-tutorial-config.xml
struts-examples-config.xml struts-config.xml
Log:
Remove the use of the deprecated action NoOpAction.
Replace by ForwardAction.
Revision Changes Path
1.2 +31 -29
jakarta-struts/web/tiles-documentation/WEB-INF/struts-tutorial-config.xml
Index: struts-tutorial-config.xml
===================================================================
RCS file:
/home/cvs/jakarta-struts/web/tiles-documentation/WEB-INF/struts-tutorial-config.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- struts-tutorial-config.xml 29 Dec 2002 21:19:01 -0000 1.1
+++ struts-tutorial-config.xml 21 Jul 2003 15:23:34 -0000 1.2
@@ -4,42 +4,39 @@
"-//Apache Software Foundation//DTD Struts Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd";>
<!--
- This is the Struts configuration file for the example application,
- using the proposed new syntax.
-
- NOTE: You would only flesh out the details in the "form-bean"
- declarations if you had a generator tool that used them to create
- the corresponding Java classes for you. Otherwise, you would
- need only the "form-bean" element itself, with the corresponding
- "name" and "type" attributes.
+ This is the Struts configuration file for the
+ Tiles-documentation "tutorial" application
-->
<struts-config>
-
- <!-- ========== Form Bean Definitions =================================== -->
+ <!-- ========== Form Bean Definitions ==================================== -->
<form-beans>
<!-- Logon form bean -->
<form-bean name="invoiceForm"
type="org.apache.struts.webapp.tiles.invoice.InvoiceForm"/>
+
+ <!-- Portal form bean -->
<form-bean name="portalPrefsForm"
type="org.apache.struts.webapp.tiles.dynPortal.PortalPrefsForm"/>
</form-beans>
- <!-- ========== Global Forward Definitions ============================== -->
+ <!-- ========== Global Forward Definitions =============================== -->
<global-forwards>
+ <!-- Forward to error page -->
<forward name="failure" path="forward.example.failure.page"/>
</global-forwards>
- <!-- ========== Action Mapping Definitions ============================== -->
+ <!-- ========== Action Mapping Definitions =============================== -->
<action-mappings>
- <!-- Main page url entry.
+ <!--
+ Main page URL entry.
This action is used to map an URL to an internal jsp.
A side effect is that the struts module is switched to the module
associated to this config file -->
@@ -66,7 +63,6 @@
<forward name="success" path="/dynFramesetPage.jsp"/>
</action>
-
<!-- Edit invoice example -->
<action path="/invoice/editInvoice"
type="org.apache.struts.webapp.tiles.invoice.EditInvoiceAction"
@@ -83,14 +79,14 @@
<forward name="success" path="main.portal.body"/>
</action>
- <!-- Dynamic Portal user lists set action : no op action forwarding to tile -->
+ <!-- Dynamic Portal user lists set action:
+ -->
<action path="/actions/myPortalPrefs"
- type="org.apache.struts.tiles.actions.NoOpAction"
- name="portalPrefsForm">
- <forward name="success" path="myDynamicPortalPreferences"/>
- </action>
+ type="org.apache.struts.actions.ForwardAction"
+ name="portalPrefsForm"
+ parameter="myDynamicPortalPreferences"/>
- <!-- Dynamic Portal user lists set tile-action : -->
+ <!-- Dynamic Portal user lists set tile-action -->
<action path="/actions/myPortalPrefs.tile"
type="org.apache.struts.webapp.tiles.dynPortal.SetPortalPrefsAction"
name="portalPrefsForm">
@@ -98,8 +94,6 @@
<forward name="portal" path="dynamic.portal.body"/>
</action>
-
-
<!-- ======================================================= -->
<!-- Rss Channel -->
<!-- ======================================================= -->
@@ -126,21 +120,29 @@
</action-mappings>
-
- <!-- ========== Tiles plug-in setting settings =================== -->
- <!-- Here we specified the tiles plug-in.
- This plug-in register appropriate Request Processor -->
- <!-- <controller processorClass="org.apache.struts.tiles.TilesRequestProcessor"
/> -->
+ <!-- ========== Request Processor Declaration =================== -->
+ <!-- The Tiles framework use a special request processor. YOU DON'T -->
+ <!-- NEED TO DECLARE IT yourself (The TilesPlugin do it for you), unless -->
+ <!-- you have created your own request processor. In this later case, -->
+ <!-- your request processor should extend the
org.apache.struts.tiles.TilesRequestProcessor -->
+ <!-- and be declared here -->
+ <!-- <controller processorClass="your.RequestProcessor" /> -->
<!-- ========== Associated Messages Ressource settings =================== -->
- <!-- Not used by tiles or this website, but needed due to a bug in actual Struts
version -->
- <message-resources
parameter="org.apache.struts.webapp.tiles.dev1-1.ApplicationResources" null="false" />
+ <!-- Uncomment the following if your webserver complains about a missing
resources. -->
+ <!-- This resource is not needed by Tiles or this example. It is just a trick to
make -->
+ <!-- Struts happy with some web server. -->
+ <!-- <message-resources
parameter="org.apache.struts.webapp.tiles.dev1-1.ApplicationResources" null="false" />
-->
+ <!-- ========== TilesPlugin settings ===================================== -->
+ <!-- You should declare this plugin if you want to use Tiles with an XML
definition file. -->
<plug-in className="org.apache.struts.tiles.TilesPlugin" >
+ <!-- Path to XML definition files -->
<set-property property="definitions-config"
value="/WEB-INF/tiles-defs.xml,
/WEB-INF/tiles-tutorial-defs.xml" />
+ <!-- Set Module-awareness to true -->
<set-property property="moduleAware" value="true" />
</plug-in>
1.4 +45 -42
jakarta-struts/web/tiles-documentation/WEB-INF/struts-examples-config.xml
Index: struts-examples-config.xml
===================================================================
RCS file:
/home/cvs/jakarta-struts/web/tiles-documentation/WEB-INF/struts-examples-config.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- struts-examples-config.xml 29 Dec 2002 21:20:06 -0000 1.3
+++ struts-examples-config.xml 21 Jul 2003 15:23:34 -0000 1.4
@@ -4,47 +4,43 @@
"-//Apache Software Foundation//DTD Struts Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd";>
<!--
- This is the Struts configuration file for the example application,
- using the proposed new syntax.
-
- NOTE: You would only flesh out the details in the "form-bean"
- declarations if you had a generator tool that used them to create
- the corresponding Java classes for you. Otherwise, you would
- need only the "form-bean" element itself, with the corresponding
- "name" and "type" attributes.
+ This is the Struts configuration file for the
+ Tiles-documentation "examples" application
-->
<struts-config>
-
-
- <!-- ========== Form Bean Definitions =================================== -->
+ <!-- ========== Form Bean Definitions ==================================== -->
<form-beans>
<!-- Logon form bean -->
<form-bean name="myPortalSettingsForm"
type="org.apache.struts.webapp.tiles.portal.PortalSettingsForm"/>
+ <!-- Menu settings form bean -->
<form-bean name="myMenuSettingsForm"
type="org.apache.struts.webapp.tiles.portal.MenuSettingsForm"/>
+ <!-- Skin settings form bean -->
<form-bean name="mySkinSettingsForm"
type="org.apache.struts.webapp.tiles.skin.LayoutSettingsForm"/>
+
</form-beans>
- <!-- ========== Global Forward Definitions ============================== -->
+ <!-- ========== Global Forward Definitions =============================== -->
<global-forwards>
+ <!-- Forward to error page -->
<forward name="failure" path="forward.example.failure.page"/>
</global-forwards>
- <!-- ========== Action Mapping Definitions ============================== -->
+ <!-- ========== Action Mapping Definitions =============================== -->
<action-mappings>
-
<!-- ======================================================= -->
<!-- Examples Portal 1.1 actions -->
<!-- ======================================================= -->
+
<!-- Dynamic Portal user lists retrieving action -->
<action path="/myPortal"
type="org.apache.struts.webapp.tiles.portal.UserPortalAction">
@@ -56,12 +52,12 @@
name="myPortalSettingsForm" >
</action>
- <!-- Portal settings page entrance : forward to appropriate page definition -->
+ <!-- Portal settings page entrance:
+ forward to appropriate page definition -->
<action path="/myPortalSettings"
- type="org.apache.struts.tiles.actions.NoOpAction"
- name="myPortalSettingsForm" >
- <forward name="success" path="examples.portal.settings.page"/>
- </action>
+ type="org.apache.struts.actions.ForwardAction"
+ name="myPortalSettingsForm"
+ parameter="examples.portal.settings.page"/>
<!-- Tiles Action associated to Tile myMenuSettings -->
<action path="/controller/myMenuSettings"
@@ -69,22 +65,23 @@
name="myMenuSettingsForm" >
</action>
- <!-- Menu Settings page entrance : forward to appropriate page definition -->
+ <!-- Menu Settings page entrance:
+ forward to appropriate page definition -->
<action path="/myMenuSettings"
- type="org.apache.struts.tiles.actions.NoOpAction"
- name="myMenuSettingsForm" >
- <forward name="success" path="examples.userMenu.settings.page"/>
- </action>
+ type="org.apache.struts.actions.ForwardAction"
+ name="myMenuSettingsForm"
+ parameter="examples.userMenu.settings.page"/>
<!-- ======================================================= -->
<!-- Tiles 1.1 Skin Settings -->
<!-- ======================================================= -->
- <!-- Skin Settings page entrance : forward to appropriate page definition -->
+
+ <!-- Skin Settings page entrance:
+ forward to appropriate page definition -->
<action path="/mySkinSettings"
- type="org.apache.struts.tiles.actions.NoOpAction"
- name="mySkinSettingsForm" >
- <forward name="success" path="examples.skin.settings.page"/>
- </action>
+ type="org.apache.struts.actions.ForwardAction"
+ name="mySkinSettingsForm"
+ parameter="examples.skin.settings.page"/>
<action path="/controller/mySkinSettings"
type="org.apache.struts.webapp.tiles.skin.LayoutSettingsAction"
@@ -95,7 +92,6 @@
type="org.apache.struts.webapp.tiles.skin.LayoutSwitchAction" >
</action>
-
<!-- ======================================================= -->
<!-- Tiles 1.1 Rss Channel -->
<!-- ======================================================= -->
@@ -107,27 +103,34 @@
<!-- Test tabs with an action URL -->
<!-- ======================================================= -->
<action path="/tabs"
- type="org.apache.struts.tiles.actions.NoOpAction">
- <forward name="success" path="examples.tabs.page"/>
- </action>
+ type="org.apache.struts.actions.ForwardAction"
+ parameter="examples.tabs.page"/>
</action-mappings>
-
- <!-- ========== Tiles plug-in setting settings =================== -->
- <!-- Here we specified the tiles plug-in.
- This plug-in register appropriate Request Processor -->
- <!-- <controller processorClass="org.apache.struts.tiles.TilesRequestProcessor"
/> -->
+
+ <!-- ========== Request Processor Declaration =================== -->
+ <!-- The Tiles framework use a special request processor. YOU DON'T -->
+ <!-- NEED TO DECLARE IT yourself (The TilesPlugin do it for you), unless -->
+ <!-- you have created your own request processor. In this later case, -->
+ <!-- your request processor should extend the
org.apache.struts.tiles.TilesRequestProcessor -->
+ <!-- and be declared here -->
+ <!-- <controller processorClass="your.RequestProcessor" /> -->
<!-- ========== Associated Messages Ressource settings =================== -->
- <!-- Not used by tiles or this website, but needed due to a bug in actual Struts
version -->
- <message-resources
parameter="org.apache.struts.webapp.tiles.dev1-1.ApplicationResources" null="false" />
+ <!-- Uncomment the following if your webserver complains about a missing
resources. -->
+ <!-- This resource is not needed by Tiles or this example. It is just a trick to
make -->
+ <!-- Struts happy with some web server. -->
+ <!-- <message-resources
parameter="org.apache.struts.webapp.tiles.dev1-1.ApplicationResources" null="false" />
-->
+ <!-- ========== TilesPlugin settings ===================================== -->
+ <!-- You should declare this plugin if you want to use Tiles with an XML
definition file. -->
<plug-in className="org.apache.struts.tiles.TilesPlugin" >
+ <!-- Path to XML definition files -->
<set-property property="definitions-config"
- value="/WEB-INF/tiles-defs.xml,
- /WEB-INF/tiles-examples-defs.xml" />
+ value="/WEB-INF/tiles-defs.xml,/WEB-INF/tiles-examples-defs.xml"/>
+ <!-- Set Module-awareness to true -->
<set-property property="moduleAware" value="true" />
</plug-in>
1.6 +22 -20 jakarta-struts/web/tiles-documentation/WEB-INF/struts-config.xml
Index: struts-config.xml
===================================================================
RCS file:
/home/cvs/jakarta-struts/web/tiles-documentation/WEB-INF/struts-config.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- struts-config.xml 29 Dec 2002 21:20:06 -0000 1.5
+++ struts-config.xml 21 Jul 2003 15:23:34 -0000 1.6
@@ -4,28 +4,20 @@
"-//Apache Software Foundation//DTD Struts Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd";>
<!--
- This is the Struts configuration file for the example application,
- using the proposed new syntax.
-
- NOTE: You would only flesh out the details in the "form-bean"
- declarations if you had a generator tool that used them to create
- the corresponding Java classes for you. Otherwise, you would
- need only the "form-bean" element itself, with the corresponding
- "name" and "type" attributes.
+ This is the Struts configuration file for the
+ Tiles-documentation application
-->
<struts-config>
- <!-- ========== Action Mapping Definitions ============================== -->
+ <!-- ========== Action Mapping Definitions =============================== -->
<action-mappings>
- <!-- ======================================================= -->
- <!-- Admin -->
- <!-- ======================================================= -->
- <!-- The standard administrative actions available with Struts -->
- <!-- These would be either omitted or protected by security -->
+ <!-- The standard administrative actions available with Tiles -->
+ <!-- These would be either omitted or protected by security constraints -->
<!-- in a real application deployment -->
+
<action path="/admin/tiles/reload"
type="org.apache.struts.tiles.actions.ReloadDefinitionsAction"/>
<action path="/admin/tiles/view"
@@ -34,19 +26,29 @@
</action-mappings>
- <!-- ========== Tiles plug-in setting settings =================== -->
- <!-- Here we specified the tiles plug-in.
- This plug-in register appropriate Request Processor -->
- <!-- <controller processorClass="org.apache.struts.tiles.TilesRequestProcessor"
/> -->
+ <!-- ========== Request Processor Declaration =================== -->
+ <!-- The Tiles framework use a special request processor. YOU DON'T -->
+ <!-- NEED TO DECLARE IT yourself (The TilesPlugin do it for you), unless -->
+ <!-- you have created your own request processor. In this later case, -->
+ <!-- your request processor should extend the
org.apache.struts.tiles.TilesRequestProcessor -->
+ <!-- and be declared here -->
+ <!-- <controller processorClass="your.RequestProcessor" /> -->
<!-- ========== Associated Messages Ressource settings =================== -->
- <!-- Not used by tiles or this website, but needed due to a bug in actual Struts
version -->
- <message-resources
parameter="org.apache.struts.webapp.tiles.dev1-1.ApplicationResources" null="false" />
+ <!-- Uncomment the following if your webserver complains about a missing
resources. -->
+ <!-- This resource is not needed by Tiles or this example. It is just a trick to
make -->
+ <!-- Struts happy with some web server. -->
+ <!-- <message-resources
parameter="org.apache.struts.webapp.tiles.dev1-1.ApplicationResources" null="false" />
-->
+ <!-- ========== TilesPlugin settings ===================================== -->
+ <!-- You should declare this plugin if you want to use Tiles with an XML
definition file. -->
<plug-in className="org.apache.struts.tiles.TilesPlugin" >
+
+ <!-- Path to XML definition file -->
<set-property property="definitions-config"
value="/WEB-INF/tiles-defs.xml" />
+ <!-- Set Module-awareness to true -->
<set-property property="moduleAware" value="true" />
</plug-in>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
