Appendix B. Configuring a Web ApplicationJavaServer Pages do not exist in a vacuum. At the very least, they will need access to numerous Java classes representing beans and the implementations of tag libraries. In addition, in any site of realistic complexity, JSPs will coexist with a set of servlets and filters and will need access to various other resources. Of course, some files will be needed to configure all this. All these pieces together comprise a Web application, and the exact layout of such applications is defined as part of the J2EE specification. Standardizing on such a format has numerous advantages. It makes it possible to develop under one application server, such as Tomcat, and to deploy under something commercially supported. It also makes it possible to package Web applications as single files called war (Web application resource) files that can be sold or otherwise distributed without needing to support hundreds of deployment scenarios.
|
