Jakarta MVC
Josh Juneau, Tarun Telang · Apress eBooks · 2022
Over the years, Jakarta EE has evolved from a servlet-centric platform to one that supports a variety of different approaches for creating web and enterprise applications. In the early days of enterprise Java, one would focus on developing servlets for building the front end, as well as the integration and business layers. This was because it was mainly focused on component orientation. Jakarta Server Pages made things get more dynamic. Developers could now split the workload between teams who would focus on HTML markup and Jakarta Server Pages tags to generate the front end and those who would focus on application logic. Jakarta Server Faces took it one step further by adhering to the Model-View-Controller pattern, whereby code logic was completely separated from page markup, creating three different tiers. This design pattern makes development more logical and long-term maintenance much easier.