This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Struts"
Jeffcityjon (talk | contribs) |
Jeffcityjon (talk | contribs) |
||
| Line 3: | Line 3: | ||
==Overview== | ==Overview== | ||
| − | [[Struts]] is an [[Apache]] framework aimed at simplifying the creation of dynamic web applications in [[Java]]. | + | [https://www.owasp.org/index.php/Category:OWASP_Java_Project [Struts]] is an [[Apache]] framework aimed at simplifying the creation of dynamic web applications in [[Java]]. |
Struts is built on a MVC architecture, which means the application is arranged into 3 primary types of code. These are know as a Model, View and Controller. The Model defines the structure of your data being processed. The View defines everything that a end user can see. The controller take the model as submitted from the page, performs business logic on the data, then decides what view should be responsible for displaying the result. | Struts is built on a MVC architecture, which means the application is arranged into 3 primary types of code. These are know as a Model, View and Controller. The Model defines the structure of your data being processed. The View defines everything that a end user can see. The controller take the model as submitted from the page, performs business logic on the data, then decides what view should be responsible for displaying the result. | ||
Revision as of 15:36, 23 January 2008
Status
Content to be finalized. First draft
Overview
[Struts] is an Apache framework aimed at simplifying the creation of dynamic web applications in Java.
Struts is built on a MVC architecture, which means the application is arranged into 3 primary types of code. These are know as a Model, View and Controller. The Model defines the structure of your data being processed. The View defines everything that a end user can see. The controller take the model as submitted from the page, performs business logic on the data, then decides what view should be responsible for displaying the result.
I will not spend any more time talking about the architecture of struts. If you would like to have more information on that topic, I suggest going to the official website.
