THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Tomcat as we all know is a Web Container available with Apache family of products. It implements Java Servlet 2.5 API and Java Server Pages 2.1 API. Apache Geronimo which is a Java EE5 certified application server which Apache Derby, Apache Active MQ, Apache AXIS, Apache Tomcat etc pre-integrated. As a result while working with Geronimo you will be working with same Tomcat engine as the standalone version of Tomcat. However there are some differences which we will discuss in upcoming sections
Implementation Analysis
While working with Geronimo you will be working with same Tomcat as the standalone Tomcat. This section will enlist the basic differences/similarities between Geronimo and Tomcat
- Both implements servlet 2.5 and JSP 2.1 API's.
- JNDI has to be configure manually in server.xml for Tomcat whereas in Geronimo,JNDI has access to all the object references managed by geronimo kernel.
- JMS is configured manually in server.xml for Tomcat whereas in Geronimo same can be achieved by GUI based Administrative Console.
- JDBC is configured manually in server.xml for Tomcat whereas in Geronimo same can be achieved by GUI based Administrative Console.
- web.xml is the default deployment descriptor for both the servers
- Geronimo has container specific deployment descriptor also know as deployment plans whereas Tomcat does not have any container specific deployment descriptor.
In geronimo most of the configuration can be done using the deployment plan geronimo-web.xml, config.xml or config-substitution.properties. Adding resources like JMS queues, connection factory, JDBC datasource etc can be easily achieved using web based Administrative console. This simplifies the configuration management versus the manual configuration done using server.xml and context.xml in Tomcat.
Best Practices
In order to overcome most migration related issues you need to figure out how each service is mapped within Tomcat and apply to Community Edition. We will enlist