Basic flow of Struts

user478636 picture user478636 · Apr 27, 2011 · Viewed 49.5k times · Source

Well I want to study Struts so I am going to begin with Struts 1, I would like to know the general flow. What files are required?

Whats the function of struts-config.xml? validation.xml? validation-rules.xml When you visit your JSP page, and an action gets fired, what happens? What does the Action and Form class do? Which class is called first when an action gets fired.

I just downloaded a sample form, and all these files are confusing at first. I would like to know whats going on to get a better idea of Struts.

Answer

user159088 picture user159088 · Apr 28, 2011

You should start with a tutorial on Struts, that will make it easy to understand :D. You can find plenty on the web, especially for Struts 1. Here is a starting point for example.

But just for the sake of it, here is a high view presentation.

First you add the Struts ActionServlet into your web.xml file and you configure it to accept requests that match a certain mapping. For Struts this is *.do (you can have whatever you want for this, *.do is just a convention in the Struts community).

Now, whatever arrives on the server with such a *.do URL pattern is sent to the ActionServlet.

Now, the content of struts-config.xml file comes into play. The ActionServlet is a front controller which just dispatches to other more appropriate resources for specific processing. Those specific resources are the Action classes.

You can have for example a LoginAction that must process requests that arrive on the login.do path. In the struts-config.xml you specify this: everything that comes on the login path must be sent to LoginAction class.

And you can have as many declarations as you want, for path x call XAction, for y call YAction etc etc.

Normally your client submits data to the server, data that he inputs into a HTML form. This data you need to process in your Action class. Now enter ActionForm.

The ActionForm is a bean that the Struts framework fills with the data from the HTML form. Instead of doing request.getParameter("foo") you can work with objects like formBean.getFoo() for example.

Once you do your processing in the Action class using the ActionForm, you then must present the results in some view (by the way, Struts is a MVC framework so you must know a stuff or two about this also).

The views are normally JSP files. When you return from your Action, you specify a "forward" location by name (i.e. to what view to go). Now again the information is in the struts-config.xml file where the name of the view is mapped to a JSP location.

The framework will then forward control to that JSP, the JSP presents the data which is then sent to the client as HTML (the client will no longer need to access JSPs directly - they must be hidden by the Struts framework).

In the new page the client again performs some requests and the process repeats.

Well, that's about as high presentation as it can get. Off course there is more than this, but you will discover them while learning about Struts.

As for the validator-rules.xml and validation.xml, those are used by the Validator framework which you can integrate with Struts by the use of a plugin (Struts has plugins you can use to add new stuff to it) to also add validation to the user's input.

Well, that is about it. You can find plenty of tutorials on the web offering more details but hope helps you get a better start.

Good luck!