<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE struts-config PUBLIC
"-//Apache Software Foundation//DTD Struts Configuration
1.2//EN"
"http://jakarta.apache.org/struts/dtds/struts-config_1_2.dtd";>
<!--
This is a blank Struts configuration file with an example
welcome action/page and other commented sample elements.
Tiles and the Struts Validator are configured using the factory
defaults
and are ready-to-use.
NOTE: If you have a generator tool to create the corresponding Java
classes
for you, you could include the details in the "form-bean"
declarations.
Otherwise, you would only define the "form-bean" element itself, with
the
corresponding "name" and "type" attributes, as shown here.
-->
<struts-config>
<!-- ============================================ Data Source
Configuration -->
<!--
<data-sources>
<data-source type="org.apache.commons.dbcp.BasicDataSource">
<set-property
property="driverClassName"
value="org.postgresql.Driver" />
<set-property
property="url"
value="jdbc:postgresql://localhost/mydatabase" />
<set-property
property="username"
value="me" />
<set-property
property="password"
value="test" />
<set-property
property="maxActive"
value="10" />
<set-property
property="maxWait"
value="5000" />
<set-property
property="defaultAutoCommit"
value="false" />
<set-property
property="defaultReadOnly"
value="false" />
<set-property
property="validationQuery"
value="SELECT COUNT(*) FROM market" />
</data-source>
</data-sources>
-->
<!-- ================================================ Form Bean
Definitions -->
<form-beans>
<!-- sample form bean descriptor for an ActionForm
<form-bean
name="inputForm"
type="app.InputForm"/>
end sample -->
<!-- sample form bean descriptor for a DynaActionForm
<form-bean
name="logonForm"
type="org.apache.struts.action.DynaActionForm">
<form-property
name="username"
type="java.lang.String"/>
<form-property
name="password"
type="java.lang.String"/>
</form-bean>
end sample -->
<form-bean name="UserLoginForm"
type="roseindia.web.struts.form.UserLoginForm">
</form-bean>
<form-bean name="UserRegisterForm"
type="roseindia.web.struts.form.UserRegisterForm">
</form-bean>
<form-bean name="UserForgetPasswordForm"
type="roseindia.web.struts.form.UserForgetPasswordForm">
</form-bean>
</form-beans>
<!-- ========================================= Global Exception
Definitions -->
<global-exceptions>
<!-- sample exception handler
<exception
key="expired.password"
type="app.ExpiredPasswordException"
path="/changePassword.jsp"/>
end sample -->
</global-exceptions>
<!-- =========================================== Global Forward
Definitions -->
<global-forwards>
<!-- Default forward to "Welcome" action -->
<!-- Demonstrates using index.jsp to forward -->
<forward
name="welcome"
path="/userregister.do"/>
</global-forwards>
<!-- =========================================== Action Mapping
Definitions -->
<action-mappings>
<!-- Default "Welcome" action -->
<!-- Forwards to Welcome.jsp -->
<action
path="/Welcome"
forward="/pages/Welcome.jsp"/>
<!-- sample input and input submit actions
<action
path="/Input"
type="org.apache.struts.actions.ForwardAction"
parameter="/pages/Input.jsp"/>
<action
path="/InputSubmit"
type="app.InputAction"
name="inputForm"
scope="request"
validate="true"
input="/pages/Input.jsp"/>
<action
path="/edit*"
type="app.Edit{1}Action"
name="inputForm"
scope="request"
validate="true"
input="/pages/Edit{1}.jsp"/>
end samples -->
<!--
<action
path="/showlist"
type="roseindia.web.struts.action.">
forward="/pages/user/showuserlist.jsp"/>
-->
<action
path="/logout"
type="roseindia.web.struts.action.Logout">
<forward name="success" path="/"/>
</action>
<action
path="/userlogin"
name="UserLoginForm"
scope="request"
validate="true"
input="/pages/user/userlogin.jsp"
type="roseindia.web.struts.action.UserLoginAction">
<forward name="success" path="/pages/user/loginsuccess.jsp"/>
<forward name="failure" path="/pages/user/userlogin.jsp"/>
</action>
<action
path="/userregister"
name="UserRegisterForm"
scope="request"
validate="true"
input="/pages/user/userRegister.jsp"
type="roseindia.web.struts.action.UserRegisterAction">
<forward name="success" path="/pages/user/registersuccess.jsp"/>
<forward name="input" path="/pages/user/userRegister.jsp"/>
<forward name="updated" path="/pages/user/updatesuccess.jsp"/>
</action>
<action
path="/userforgetpassword"
name="UserForgetPasswordForm"
scope="request"
validate="true"
input="/pages/user/forgetpassword.jsp"
type="roseindia.web.struts.action.UserForgetPasswordAction">
<forward name="success" path="/pages/user/passwordSend.jsp"/>
<forward name="failure" path="/pages/user/forgetpassword.jsp"/>
</action>
</action-mappings>
<!-- ============================================= Controller
Configuration -->
<controller
processorClass="org.apache.struts.tiles.TilesRequestProcessor"/>
<contoller>
<set-property property="locale" value="true"/>
</contoller>
<!-- ======================================== Message Resources
Definitions -->
<message-resources parameter="MessageResources" />
<!-- =============================================== Plug Ins
Configuration -->
<!-- ======================================================= Tiles
plugin -->
<!--
This plugin initialize Tiles definition factory. This later can takes
some
parameters explained here after. The plugin first read parameters from
web.xml, thenoverload them with parameters defined here. All parameters
are optional.
The plugin should be declared in each struts-config file.
- definitions-config: (optional)
Specify configuration file names. There can be several comma
separated file names (default: ?? )
- moduleAware: (optional - struts1.1)
Specify if the Tiles definition factory is module aware. If
true
(default), there will be one factory for each Struts module.
If false, there will be one common factory for all module. In this
later case, it is still needed to declare one plugin per
module.
The factory will be initialized with parameters found in the
first
initialized plugin (generally the one associated with the
default
module).
true : One factory per module. (default)
false : one single shared factory for all modules
- definitions-parser-validate: (optional)
Specify if xml parser should validate the Tiles configuration
file.
true : validate. DTD should be specified in file header (default)
false : no validation
Paths found in Tiles definitions are relative to the main context.
-->
<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>
<!-- =================================================== Validator
plugin -->
<plug-in className="org.apache.struts.validator.ValidatorPlugIn">
<set-property
property="pathnames"
value="/WEB-INF/validator-rules.xml,/WEB-INF/validation.xml"/>
</plug-in>
</struts-config>
