- Centralized File-Based Configuration.
Struts values/mapping is represented in XML or property files. This loose coupling means that many changes can be made without modifying or recompiling Java code, and that wholesale changes can be made by editing a single file. According to Struts Training in Chennai this approach also lets Java and Web developers focus on their specific tasks (implementing business logic, presenting certain values to clients, etc.) without needing to know about the overall system layout.
- HTML Tags.
Struts provide a set of custom JSP tags to create HTML forms that are associated with JavaBeans components. This bean/form association serves two useful purposes:
It lets you get initial form-field values from Java objects.
It lets you redisplay forms with some or all previously entered values intact.
- Form Field Validation
- “Plumbing code” contained within the Struts framework.
Mapping HTTP request parameters to Java objects is handled by Struts, for example. You don’t have to do it. This allows you to focus more on the domain problem instead of building infrastructure.
- Good documentation & plenty of books
If you have to leave the project and/or someone else has to maintain it then using a well-known and well documented framework will make that job much easier. A homebrewed framework just can’t match that.
- Broad user testing
Since Struts is used in plenty web-apps the framework will get looked at by many more eyes than anything you could write alone. Usually, but not always, that means any problems you have will have been seen by someone else (and hopefully resolved) first.
These are the few of the many advantages of using struts.