Answer Posted / pradip mishra(geit dehradun(b-

yes but it is not necessarly to import alwase in struts-
config.xml, u may change on web.xml<?xml version="1.0"
encoding="UTF-8" ?>

<!DOCTYPE struts-config PUBLIC
"-//Apache Software Foundation//DTD Struts
Configuration 1.2//EN"
"http://jakarta.apache.org/struts/dtds/struts-
config_1_2.dtd">


<struts-config>
<form-beans>
<form-bean name="NewStrutsActionForm"
type="p.NewStrutsActionForm"/>

</form-beans>

<global-exceptions>

</global-exceptions>

<global-forwards>
<forward name="welcome" path="/Welcome.do"/>
</global-forwards>

<action-mappings>
<action input="/welcomeStruts.jsp"
name="NewStrutsActionForm" path="/xx" scope="session"
type="p.NewStrutsAction">
<forward name="success"
path="/welcomeStruts.jsp"></forward>
<forward name="fail"
path="/Hello1.jsp"></forward>
<forward name="s12"
path="/welcomeStruts.jsp"></forward>
</action>



<action path="/Welcome"
forward="/welcomeStruts.jsp"/>
</action-mappings>

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

<message-resources
parameter="com/myapp/struts/ApplicationResource"/>

<!-- ========================= 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" >
<set-property property="definitions-config"
value="/WEB-INF/tiles-defs.xml" />
<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>

What is interceptor? And life cycle methods of interceptor?

1015

---

What does the term struts mean?

973

---

Do you need an alignment after replacing struts?

924

---

What is the use of web xml in struts2?

892

---

Are the struts tags xhtml compliant ?

928

---

What is the difference between struts1 and struts2?

909

---

How can we handle exceptions thrown by application in Struts2?

923

---

What is controller in struts2?

1107

---

How do I install struts?

1000

---

What are the cons of struts 2?

993

---

How is a lookup dispatch action created?

988

---

Explain design patterns which is used in struts?

954

---

What is the purpose of @stringlengthfieldvalidator annotation?

1085

---

What are the features of struts?

1002

---

Does struts include its own unit tests?

1005

---