✔ STRUTS 2 CHAPTERS:-
1. Struts2 Overview
2. Struts2 Architecture
3. Struts2 Configuration Files
4. Action in Struts2
5. Action in Struts2 by using Pojo Class
6. Action in struts2 by Implementing Action Interface
7. Action in Struts2 by Extending Action Support Class
8. Struts2 Hello World Example
9. Multiple Configuration File in Struts2
10. OGNL in Struts2
11. Value Stack in Struts2
12. Interceptors in Struts2
13. Struts2 Execandwait Interceptor
14. Struts2 Custom Interceptor
15. Struts2 Result type
16. Struts2 Redirect result type
17. Struts2 Validation Framework
18. Struts2 Validation by Built in validators
19. Struts2 i18n
20. Struts2 Zero Configuration by convention approach
21. Struts2 Zero Configuration by annotation Approach
22. Dispatch Action Functionality in Struts2
23. Dynamic method invocation in Struts2
24. Struts2 UI Tags
25. Struts2 Control Tags
26. Struts2 Data Tags
27. Struts2 and tiles integration
28. Struts2 and Quartz2 Schedular
29. Struts2 Interview Questions and Answers
1. Struts2 Overview
2. Struts2 Architecture
3. Struts2 Configuration Files
4. Action in Struts2
5. Action in Struts2 by using Pojo Class
6. Action in struts2 by Implementing Action Interface
7. Action in Struts2 by Extending Action Support Class
8. Struts2 Hello World Example
9. Multiple Configuration File in Struts2
10. OGNL in Struts2
11. Value Stack in Struts2
12. Interceptors in Struts2
13. Struts2 Execandwait Interceptor
14. Struts2 Custom Interceptor
15. Struts2 Result type
16. Struts2 Redirect result type
17. Struts2 Validation Framework
18. Struts2 Validation by Built in validators
19. Struts2 i18n
20. Struts2 Zero Configuration by convention approach
21. Struts2 Zero Configuration by annotation Approach
22. Dispatch Action Functionality in Struts2
23. Dynamic method invocation in Struts2
24. Struts2 UI Tags
25. Struts2 Control Tags
26. Struts2 Data Tags
27. Struts2 and tiles integration
28. Struts2 and Quartz2 Schedular
29. Struts2 Interview Questions and Answers
Template:
A template is a predefined pattern or format used as a guide to making something.
Tile:
A tile specifies a part of the whole page.
Generally a website is the combination of different components or parts. Most of these parts are common on every page and mainly one part is changed (body section). If we use these common components in every page it will increase the complexity and code duplicity. Later on if any changes have to made in the common part of the website it needs to be done in every page. To simplify this we use the concept of template. Let our website have header, footer, menu and body parts. These are known as tiles in template. A part can be of static or dynamic content. Tiles framework uses the tiles.xml file to manage all tiles.
Advantages of tiles framework:
- 1. Easy modification.
- 2. Code reusability.
For single tile definition in struts 2 application use following entry in web.xml:
For multiple tiles definition in struts 2 application use following entry in web.xml:
Example:
index.jsp
web.xml
struts.xml
Login.java
tiles.xml
welcome.jsp
body.jsp
header.jsp
footer.jsp
menu.jsp
welcome.jsp
admin.jsp
user.jsp
Output:
Click on Admin link.
Click on User link.
No comments:
Post a Comment