Answer / narendher sharma

<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>
<form-bean name="ufBean"
type="A.Form.loginform"/>
</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="/Welcome.do"/>
</global-forwards>


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

<action-mappings>
<!-- Default "Welcome" action -->
<!-- Forwards to Welcome.jsp -->
<action
path="/Welcome"
forward="/pages/Welcome.jsp"/>

<action
path="/login"
type="A.Action.loginAction"
name="ufBean"
scope="request"

>

<forward name="success" path="/success.jsp"/>
<forward name="failure" path="/Failer.jsp"/>
</action>

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


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

<controller

processorClass="org.apache.struts.tiles.TilesRequestProcesso
r"/>


<!-- ======================================== Message
Resources Definitions -->

<message-resources parameter="ApplicationResources" />


<!-- =============================================== 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>
These are the main things in struts -config.xml

Answer / narendher sharma

<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>
<form-bean name="ufBean"
type="A.Form.loginform"/>
</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="/Welcome.do"/>
</global-forwards>


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

<action-mappings>
<!-- Default "Welcome" action -->
<!-- Forwards to Welcome.jsp -->
<action
path="/Welcome"
forward="/pages/Welcome.jsp"/>

<action
path="/login"
type="A.Action.loginAction"
name="ufBean"
scope="request"

>

<forward name="success" path="/success.jsp"/>
<forward name="failure" path="/Failer.jsp"/>
</action>

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


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

<controller

processorClass="org.apache.struts.tiles.TilesRequestProcesso
r"/>


<!-- ======================================== Message
Resources Definitions -->

<message-resources parameter="ApplicationResources" />


<!-- =============================================== 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>
These are the main things in struts -config.xml

struts 1.3 features?

1 Answers   Integra, Zensar,

---

is it possible to see actionservlet in my system. if yes how

5 Answers  

---

Hi All thanks in advance, iam new to j2ee currently in my project we r using struts with hibernate can i have one sample application like CRUD application with code or any tutorials liks r ebooks plz....?

1 Answers   IBM,

---

where you use thread in your java project?

1 Answers   Cap Gemini,

---

What is struts2 namespace?

0 Answers  

---

what are tiles in struts?

3 Answers   Wipro,

---

Can we write our own ActionServlet for front controller of Struts Applications?

2 Answers   NIIT,

---

What is actioninvocation?

0 Answers  

---

What configuration files are used in struts?

0 Answers  

---

What does modeldriven interceptor?

0 Answers  

---

is it necessary to write struts-confing.xml ,what tags are important in that xml file?

2 Answers  

---

Is form beans are serializable or not?

11 Answers   College School Exams Tests, Magna Infotech,

---