Lukasz Lenart
0fd3d7a2fb
* docs: add creating-version-notes skill and page template Covers Version Notes pages on the cwiki for every maintenance line - 6.x and 7.x share one structure, so the release line changes the data, not the process. The published pages show that cloning the previous release's page reliably leaves a half-updated link, differently each time, so the skill starts from a template instead. The template corrects three defects the published pages carry: a malformed code-macro parameter, hard-coded macro ids duplicated across releases, and trailing empty divs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs: extend creating-version-notes with the Migration Guide step Exercising the skill on Version Notes 6.11.0 surfaced four rules it was missing: - The page is a child of Migration Guide (13981), which is also the index; a page not listed there is unreachable. Records how to update that section safely and why its version diff renders empty even when the edit landed. - Reconcile through the ticket's linked PR files. WW-5630 reads "Performance Issue SecurityMemberAccess" but was fixed in ConfigParseUtil, so grepping commit subjects or the class in the title wrongly concludes the backport is missing. - Patch-level dependency bumps ship untick eted by design, so a pom version ahead of the ticket text is expected rather than a reconciliation gap. - The Staging Repository block is included on every line, not an open decision. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs: cover the GitHub release notes in creating-version-notes A release also has GitHub release notes at the STRUTS_X_Y_Z tag, and the generated body needs two corrections before it is fit to publish. Entries are split into What's Changed and a nested Dependencies section by whether they carry a WW ticket, not by author: a Dependabot PR with a ticket is release content and stays above, while an untick eted dependency bump from anyone moves down. More importantly, the generated Full Changelog range is not trustworthy. GitHub picks the previous tag by reachability, and our release branches get renamed and re-imported, so it reaches too far back - for 6.11.0 it chose STRUTS_6_8_0 and listed 88 entries that had already shipped in 6.9.0 and 6.10.0. The range must be verified with git log PREV..THIS, which works across unrelated histories. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
The Apache Struts web framework
The Apache Struts web framework is a free open-source solution for creating Java web applications.
Documentation
More information can be found on the homepage. Please read the Security Guide, and the JavaDocs can be browsed. Questions related to the usage of Apache Struts should be posted to the user mailing list.
Description
Web applications differ from conventional websites in that web applications can create a dynamic response. Many websites deliver only static pages. A web application can interact with databases and business logic engines to customize a response.
Web applications based on JavaServer Pages sometimes commingle database code, page design code, and control flow code. In practice, we find that unless these concerns are separated, larger applications become difficult to maintain.
One way to separate concerns in a software application is to use a Model-View-Controller (MVC) architecture. The Model represents the business or database code, the View represents the page design code, and the Controller represents the navigational code. The Struts framework is designed to help developers create web applications that utilize an MVC architecture.
The framework provides three key components:
- A “request” handler provided by the application developer that is mapped to a standard URI.
- A “response” handler that transfers control to another resource which completes the response.
- A tag library that helps developers create interactive form-based applications with server pages.
The framework’s architecture and tags are buzzword compliant. Struts works well with conventional REST applications and with technologies like SOAP and AJAX.
The Apache Struts Project
The Apache Struts Project is the open source community that creates and maintains the Apache Struts framework. The project consists of a diverse group of volunteers who share common values regarding collaborative, community-based open source development. The Apache Struts Project is proud to share these values with our parent organization: The Apache Software Foundation.
The project is called “Struts” because the framework is meant to furnish the “invisible underpinnings” that support professional application development. Struts provides the glue that joins the various elements of the standard Java platform into a coherent whole. Our goal is to leverage existing standards by producing the missing pieces we need to create enterprise-grade applications that are easy to maintain over time.
The Apache Struts Project offered two major versions of the Struts framework. Currently we are only maintaining the Struts 2 version. It is recommended to upgrade all Struts 1.x applications to Struts 2. Please do not start new application development using Struts 1.x, as we are no longer issuing security patches.
Struts 2 was originally known as WebWork 2. After working independently for several years, the WebWork and Struts communities joined forces to create Struts 2. The 2.x framework is the best choice for teams who value elegant solutions to difficult problems.
Why should you use Apache Struts?
Apache Struts is a modern, maintained and full-featured web framework. As it has been around for years and grown a huge user base it is unlikely it will go away anytime soon. Not only that, we have dedicated users and developers on the project. Apache Struts is licensed under the Apache License 2.0 and this will not change. We maintain a clean IP and you are “safe” to use the project. Sometimes you are not “safe” to use a project when a company controls the SCM. Access to Source Code doesn’t mean it is free. With Apache Struts, you are not only free to “do what you want with it”, you can even contribute (which is not always the case). And best of all: you can become a part of the core team too.
It is usually very easy to integrate other technologies with Apache Struts. If you are using an ORM like Apache Cayenne, Hibernate or JDBC, you will not have any restrictions. Apache Struts is not even tied too much to a frontend technology. In old days it was JSP, then came Velocity and Freemarker. Nowadays you might build your web application with just static HTML and AngularJS. Or you might want to use Sitemesh or Tiles. This all is no problem due to Struts' elegant and easy-to-use extension mechanisms.
Unlike other, component-oriented frameworks, we do not aim to hide the stateless nature of the web. We think it is perfectly acceptable to build upon a Request/Response cycle. We also think the MVC pattern is not so bad, just because it is old. In fact, we believe the Apache Struts architecture is clean and easy to understand.
Of course, if you wish to build components on the server side which render on the front end side, you will most likely not want Struts. This is a different approach which promises to reduce the amount of HTML/JavaScript knowledge needed and to create reusable components for the view layer. Projects like Wicket and Tapestry serve this purpose very well. As with every framework, you need to decide if it makes sense for you to build components or if you prefer the Struts approach.
Commercial Support
The Apache Struts community does not offer commercial support by itself, but we maintain a list of companies offering commercial support on our website.
Some Apache Struts maintainers are working with Tidelift to provide commercial support and invest paid working time in the improvement of the Apache Struts framework. For more information, visit the Tidelift resources regarding Apache Struts
Thank you
YourKit is kindly supporting open source projects with its full-featured Java Profiler. YourKit is the creator of innovative and intelligent tools for profiling Java and .NET applications. As an Apache committer, you can get a free license at YourKit's open source sponsorship program.