Scribd
Upload
8 views1 page

Struts Workflow and ActionForm Guide

This document provides a high-level overview of how Struts works. It explains that Struts uses an ActionServlet to dispatch requests with a *.do pattern to Action classes specified in the struts-config.xml file. ActionForms are used to access form data and pass it to the Action classes for processing, which then return a view, typically a JSP, to present the results.

Uploaded by

prema
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
8 views1 page

Struts Workflow and ActionForm Guide

This document provides a high-level overview of how Struts works. It explains that Struts uses an ActionServlet to dispatch requests with a *.do pattern to Action classes specified in the struts-config.xml file. ActionForms are used to access form data and pass it to the Action classes for processing, which then return a view, typically a JSP, to present the results.

Uploaded by

prema
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

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 [Link] 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 [Link] file comes into play. The ActionServlet is a front
controllerwhich 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 [Link]. In the [Link] 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 YActionetc 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 [Link]("foo") you can work with objects
like [Link]() 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 Actio

You might also like