Java Tutorial - Java Script :
Needs and Features Analysis
In the previous section, we discussed the many benefits of offering a Webbased interface for enterprise applications. So, what are the things that we are looking for in a servlet container? What features are required, and which
would we just like to have? Simply stated, the basic requirements for a servlet container are as follows:
Support for Java servlets and JavaServer pages: First and foremost, we need the basic functionality of a servlet container with JSP support. This is the most basic requirement.
Conformance with J2EE standards: We may not require conformance to the most current version of the standard but we do want a conforming implementation. The rationale here is that we want to be able to develop software on this platform that can be easily rehosted if necessary. If the container conforms to the standards, and we restrict our development teams to staying within the scope of the standard, we can achieve this. The standards in question here are version 2.3 of the Java Servlet specification and version 1.2 of the JavaServer Pages specification. We need the product that we select not only to conform to these standards but also to be developed to support the future changes in the standard.
Support for standalone operatio:. Standalone operation of the servlet container is important for developers and for small applications. It is easier to configure and maintain a servlet container if it does not need
tobe integrated with a Web server. We should potentially be able to allow each developer to have a personal copy of the servlet container.
Support for integration with Web server: In addition to wanting to be able to have standalone operation, we also want to have the ability to integrate the product with a Web server. This is important for large-scale
deployment. The Web server can be used to provide load balancing and to reduce the load on the servlet container by handling static content.
Project stability and continuing support:The servlet container is a core piece of functionality in our platform. We want to make sure that development on the product is not likely to end and that there will be continuing support for it. Remember that we pointed out earlier that there have been a number of servlet containers that were created and are now orphaned or are not being maintained—we don’t want this to happen to the product we chose.
