<!-- ========================================= 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="error"
            path="/jsp/error.jsp"/>           
    </global-forwards>

<!-- =========================================== Action Mapping Definitions -->

    <action-mappings>
            <!-- Default "Welcome" action -->
            <!-- Forwards to 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  
   name="projectlistform"   
   path="/projectlist"
   scope="request"
   type="team4.action.ProjectListAction"
   validate="false">
   <forward name="right" path="/jsp/projectlist.jsp" />
   <forward name="fail" path="/jsp/error.jsp" />
  </action>
  <action  
   name="projectdetailform"   
   path="/projectdetail"
   scope="request"
   type="team4.action.ProjectDetailAction"
   validate="false">
   <forward name="right" path="/jsp/projectdetail.jsp" />
   <forward name="fail" path="/jsp/error.jsp" />
  </action>
  <action  
   name="projectaddform"   
   path="/projectadd"
   scope="request"
   type="team4.action.ProjectAddAction"
   validate="false">
   <forward name="add" path="/jsp/projectadd.jsp" />
   <forward name="list" path="/projectlist.do" />

   <forward name="fail" path="/jsp/error.jsp" />
  </action>
  <action  
     
   path="/projectshowpict"
   scope="request"
   type="team4.action.ProjectShowPictAction"
   validate="false">
   
  </action>
    <action  
     
   path="/projectdelete"
   scope="request"
   type="team4.action.ProjectDeleteAction"
   validate="false">
   <forward name="fail" path="/jsp/error.jsp" />
   <forward name="list" path="/projectlist.do" />
  </action>
    <action  
   name="projecteditform"   
   path="/projectedit"
   scope="request"
   type="team4.action.ProjectEditAction"
   validate="false">
   <forward name="edit" path="/jsp/projectedit.jsp" />
   <forward name="list" path="/projectlist.do" />

   <forward name="fail" path="/jsp/error.jsp" />
  </action>
  <action  
   name="studentlistform"   
   path="/studentlist"
   scope="request"
   type="team4.action.StudentListAction"
   validate="false">
   <forward name="right" path="/jsp/studentlist.jsp" />
   <forward name="fail" path="/jsp/error.jsp" />
  </action>
    </action-mappings>

<!-- ============================================= Controller Configuration -->

    <controller
       processorClass="org.apache.struts.tiles.TilesRequestProcessor"/>

<!-- ======================================== 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>