Java Tutorial - Java Script : Selection

Java Tutorial - Java Script :

Selection


Both Jetty and Tomcat are excellent products. Both meet our primary criteria and requirements. Either product would be a suitable choice. This gives us the advantage that either decision can be viewed as the right one. However, we must select one product to use as we move forward. In this case, we select Tomcat. There are several reasons for selecting Tomcat over Jetty:
·  Tomcat is a more popular application server than Jetty and so it should be easier to find people who are familiar with it and who can support it.
·  Tomcat and Jasper are also the official reference implementations of the Servlet and JSP specifications, respectively. This implies that there should be a commitment by both the Tomcat team and those that contribute to the specification to make sure that Tomcat evolves with the specifications.
·  As part of the Apache project, it is expected that Tomcat will also continue to support integration with the Apache Web server as it and the connectors to it mature.
·  Finally, Tomcat’s built-in management tools seem to be more mature and functional than those provided by Jetty.

So, for our purposes in this book, we select Tomcat. However there are a number of times when Jetty may be the better choice. Jetty would be the preferred choice if server size were a constraint. It would also be the choice if we needed to embed an application server into a larger software product. Jetty’s size and its support J2ME also make it the choice for embedded and palm-size applications.