Application layering is applying the idea of separation of concerns to your software. Understanding how each of the J2EE technologies fits within an overall architectural road map is the key to writing flexible, maintainable applications whose components do not step on each other's toes. In explaining our approach, we have described these five layers in detail:
We've demonstrated how this five-layer architecture can map to the different parts of the J2EE standard, and how you can use the WebSphere tool set and runtime to build and deploy applications that use those technologies. We hope that our architectural road map and the comparisons of different approaches to similar ends (like JSP and XML/XSLT) have helped you understand how to choose which approach to take.
Also, we have discussed application responsibilities that developers must apply to all application development efforts. Implementing these activities consistently using a design that is extendible facilitates reuse and minimizes side effects when requirements change. Moreover, standardizing these services across all applications can yield efficiencies in determining and communicating new development and maintenance activities.