Struts Tutorials

11. 7 Best Practices of Struts

By: Emiley J. : 2008-08-13

Description: This tutorial lists 7 Best practices of Struts.

12. Origin and Architecture of Struts

By: Fanny Ong : 2007-10-12

Description: Craig McClanahan originally wrote the Struts framework, mostly while on his Memorial Day vacation in 2000! The framework was subsequently donated by Craig to the Apache Software Foundation. The fact that it was mostly written in one weekend should suggest to you that it’s a very simple framework.

13. Struts-GUI and Struts Console

By: Lakshmi : 2007-10-01

Description: When the development begins, the struts-config.xml is always small and manageable. But as time passes and features are added, the file continues to grow to become a monster. Splitting the application into modules definitely helps, but modules can be relatively large too. There are better ways to mange the strutsconfig.xml than simply editing by hand or even an XML editor. Some of the

14. XDoclet struts-config.xml in Struts

By: Kamini : 2007-10-01

Description: XDoclet based management of struts-config.xml is a entirely different concept. In XDoclet approach, there is no struts-config.xml at all! In the XDoclet approach, there is no struts-config.xml at all! All the requisite information linked to the and are specified in the Action and Form

15. Guidelines for Struts Application Development

By: Jagan : 2007-10-01

Description: Struts application development in enterprise applications requires discipline. We are not referring to any particular methodology; just some guidelines for Struts based application development for enterprise applications. In this section a stepby-step approach for Struts application development cycle is provided.

16. Handling Duplicate Form Submissions in Struts

By: Ivan Lim : 2007-10-01

Description: Duplicate form submissions are acceptable in some cases. Such scenarios are called idempotent transitions. When multiple submissions of data are not critical enough to impact the behavior of the application, duplicate form submissions do not pose a threat.

17. DispatchAction in Struts

By: Grenfel : 2007-10-01

Description: DispatchAction is another useful built-in Struts Action. However you cannot use it as is. You will have to extend it to provide your own implementation. An example will make things clear. Consider an online credit card application. Customers fill the credit card application online. The bank personnel get a List screen as shown in Figure below and they can act in one of four ways - Approve, Reject or Add Comment. Consequently there are three images each being a .

18. IncludeAction in Struts

By: Fazal : 2007-10-01

Description: IncludeAction is much like ForwardAction except that the resulting resource is included in the HTTP response instead of being forwarded to. It is rarely used. Its only significant use is to integrate legacy applications with Struts transparently. Consider a web site that aggregates information from disparate sources – some of which are non-Struts. The JSP for such a web site consists of s to include different resources. One of such that might be as follows:

19. Protecting JSPs from direct access in Struts

By: Emiley J : 2007-10-01

Description: According to the Model 2 paradigm, the view is always served by the controller and should not be requested explicitly from any other view. In reality a JSP can always navigate to another JSP when the JSPs are placed anywhere in a WAR other than the WEB-INF directory (or its sub-directories). Similarly a user can type in the name of the JSP in the URL bar and invoke the JSP. The web application specification does not disallow such access. Actually this makes sense. The specification should not prevent anybody from coding using the Model 1 paradigm. Consequently your JSPs are exposed to the external world for nosy users to cause unnecessary problems, for hackers to exploit any vulnerability in the system. If you are wondering what the problem is with allowing direct access to JSPs, well, here are some.

20. ForwardAction in Struts

By: Daniel Malcolm : 2007-10-01

Description: ForwardAction is the one of the most frequently used built-in Action classes. The primary reason behind this is that ForwardAction allows you to adhere to MVC paradigm when designing JSP navigation. Most of the times you will perform some processing when you navigate from one page to another. In Struts, this processing is encapsulated in the Action instances. There are times however when all you want to do is navigate from one page to another without performing any processing. You would be tempted to add a hyperlink on the first page for direct navigation to the second. Watch out! In Model 2 paradigm, a straight JSP invocation from another JSP is discouraged, although not prohibited. For instance, suppose you want to go from PageA.jsp to PageB.jsp in your Struts application. The easy way of achieving this is to add a hyperlink in PageA.jsp as follows: