What does Java's Struts Framework do?

Struts is a stunning, scalable, open-source framework for building Java web applications. Model-View-Controller (MVC) architecture is used to construct web applications utilizing it.

Struts 2 was formerly known as Webwork 2. Later, the two frameworks—webwork and struts—were combined to produce struts 2, a new version of struts.

Webwork Plus Struts 1 = Struts 2.

Struts 2 characteristics

1. POJO form: 

Struts 2 does not require action forms. Any POJO class can accept form input.

2. POJO Activities: 

An Action class is not necessary for Struts 2. Any POJO class can be used to construct an Action class.

3. Improved Support for Tags: 

Struts 2 provides a variety of tags to simplify the development process.

4. Template Support: 

Struts 2 offers the ability to use templates to build common look views.

5. Support for Simple Integration: 

Struts 2 applications can be easily connected with other frameworks, such as spring, hibernate, etc.

6. Support for AJAX: 

Struts 2 provides ajax capabilities via ajax tags.

7. Support for Enhanced Results:

 Tools like JFreeChart, Jasper Reports, and others can be utilized to generate more distinctive results.

Sturct2 Benefits

1. In Struts 1, action classes are required to extend an abstract base class.
2. Struts 1 Action is thread-safe because it is a singleton.
3. The servlet API is a need for Struts 1 Action, as both the HTTP Servlet Request and HTTP Servlet Response must be provided in the execute method.
4. Struts 1 makes use of the Action Form's object to receive form input.
5. Struts 1 employs the JSTL expression language.
6. Struts 1 uses the standard JSP approach to connect objects into the page context.
7. Type conversion with Struts 1 is less versatile.
8. Struts 1's validate function is used to manually validate the Action Form.

Struct2 Drawbacks

1. Struts 2 does not mandate that action classes extend any abstract classes. The Action interface might be employed.

      2. Struts 2 actions are not thread-safe.

3. Struts 2 Actions do not require the servlet API.
4. Struts 2 does not require an Action Form.
5. Struts makes use of the "Object Graph Notation Language" (OGNL) expressive language. 6. Struts 2 uses Value Stack technology to connect values to views.
6. Struts 2 provides a more flexible type of conversion.
7. Struts 2 enables manual validation by using the validate function. Also included is the XWork Validation framework.

Struts 2's basic MVC architecture:

Model View Controller, or MVC as it is more commonly referred to when used to create online applications, is the name of the software design pattern. A is made up of the following three elements.

Pattern for Model View Controller:

1. Model – The data are kept at the most basic level possible.
2. View – This is in charge of displaying all or some of the data to the user.
3. Controller - The software that controls how the Model and View communicate with one another.

The Model:

The model is in charge of maintaining the data for the application. Both the controller's and the view's requests for it to update itself are met by it.

The Opinion

This phrase describes the display format that data takes after being chosen for presentation by a controller. They are script-based templating systems that are very easy to integrate with AJAX technologies, just as JSP, ASP, and PHP.

A controller

The task of interacting with the data model objects and responding to user input falls to the Controller. The controller receives the input and evaluates it before performing the business action that modifies the state of the data model.

Sturt2 Construction:

At its most fundamental, Struts2 is a pull-MVC (or MVC2) framework. The Model-View-Controller pattern is implemented by Struts2 using the following five key components:

1. Conduct
2. Interception 
3. Value Stack/OGNL
4. Results / Results Types
5. Check out the technology

Struts 2 differs slightly from a typical MVC framework despite some commonality in that the action takes on the role of the model rather than the controller.

The following diagram depicts the Model, View, and Controller parts of the Struts2 high-level architecture. This model is composed of actions, the controller employs interceptors and a Struts2 dispatch servlet filter, and the display mixes results and result sorts. There is a linking, enabling, and common thread provided by the value stack and OGNL.

Interceptor Sturt2

Interceptors conceptually correspond to servlet filters or the JDK's Proxy class. Interceptors enable cross-cutting functionality to be provided independently of the action and framework. Interceptors can be used to accomplish the following:

1. Preprocessing logic is offered before calling the action.
2. Once the action is invoked, offer logic for postprocessing.
3. capturing exceptions so that other processing is possible

strut default interceptors that are frequently used 2.

1. Alias: It makes it possible to use different alias names for the same parameters in different requests.
2. Checkboxes:  managed by adding a false value for checked but unchecked checkboxes.
3. Conversion error: This is used to add conversion errors to the field errors for the activity.
4. Execute and wait: Using this method, users are forwarded to a waiting page while an action is being completed.
5. I18n: It keeps track of the active locale for the session. It provides instruments for localization and globalization.
6. Debugging: It provides the developer with debugging support.
7. Exception: By mapping an exception from an action to the result, it provides the ability to automatically manage exceptions.
8. File Uploading: The ability to upload files is a feature of this function.
9. Logger: The logger displays the name of the action that was carried out.
10. Validation: It provides support for validation.