Place a context definition in /META-INF/context.xml – this is the preferred 5.5 per-application method as indicated here. The context file will be copied when deployed to [tomcat]/conf/Catalina/localhost/[webapp_name].xml.

This context file is the where the majority of the jndi configuration will take place. Any datasources configured here will need access to the identified driver class. Put your jars in $CATALINA_HOME/common/lib.

Example:

<context
    crossContext="true"
    reloadable="true"
    displayName="Barack's Datasource" >

        <resource
            name="aspiring.presidentDS"
            type="javax.sql.DataSource"
            driverClassName="oracle.jdbc.OracleDriver"
            maxIdle="2"
            maxWait="5000"
            validationQuery="select count(*) from elections.election_name"
            username="bobama"
            password="top_secret"
            url="jdbc:oracle:thin:@aspiring.com:1525:bobama"
            maxActive="20"
            removeAbandoned="true"
            removeAbandonedTimeout="60"
            logAbandoned="true"/>
</context>

Important Note: Prior to Tomcat 5.5, a “path” attribute was required for Context elements (starting with 5.5, the path attribute must not be used except when statically defining a Context in server.xml, as it will be inferred from the Context fragment filename.

Note: Apparently Loggers are not configured in within the Context element anymore.

Note: While the [appname].xml is added to /conf/Catalina/localhost/[webapp_name].xml automatically, it does not appear to be overwritten or cleaned up.

As far as spring goes, the only change is the need to prepend java:/comp/env/ to the jndi name. So for example, something like this:

	<bean id="webappDataSource" class="org.springframework.jndi.JndiObjectFactoryBean">
		<property name="jndiName" value="com.aspiring.present.bobamaDS" />
	</bean>

will become this:

	<bean id="webappDataSource" class="org.springframework.jndi.JndiObjectFactoryBean">
		<property name="jndiName" value="java:/comp/env/com.aspiring.president.bobamaDS" />
	</bean>

Resources:

Tomcat 5.5 Classloader explanation

Tomcat 5.5 JNDI Guide

Tomcat JNDI Example HowTo

Here are the configuration entries I made to get pine working with my dreamhost account:

• personal-name: Enter your name or nickname; this is what receiver of your mail message will see
• user-domain: Enter your domain name. For example, my site is
  http://ehemminger.org so I entered, ehemminger.org.
• smtp-server: This is sometimes the tricky part. If I were remoting into my hosted account, I could use dreamhost’s smtp server, like this: mail.ehemminger.org/user=jeff@ehemminger.org. But I’m not, I’m using pine from my desktop. So instead, I’ll use my service provider’s smtp server. I’m using Marianas Cablevision, so I checked their site and found that the smtp server is: smtp.guam.net
• inbox-path: At Dreamhost, your Inbox path is “Inbox”. In Pine, you must indicate the server, your username, and the folder. The server and user name are contained in curly braces. For example, I entered: {mail.ehemminger.org/user=jeff@ehemminger.org}Inbox
• default-fcc: I set my default fcc (forward carbon copy) to my Sent mail folder. This way, I can keep a
  copy of every message I send. Example: {mail.ehemminger.org/user=jeff@ehemminger.org}Inbox.Sent

                              Bootstrap
                                  |
                               System
                                  |
                               Common
                              /      \
                         Catalina   Shared
                                     /   \
                                Webapp1  Webapp2 .. etc

Classloader rules:

* Classloaders will only load the “same” class once.
* Two classes are only the “same” if they have the same name, and were loaded by the same classloader.
* When your webapp references a class, if it’s not already loaded, the search order goes:
yourWebapp –> Shared –> Common –> System –> Bootstrap

You can make Tomcat point to your source codebase and autodeploy automatically. Copy the following into your tomcat/conf/Catalina/localhost/myproject.xml

Assuming that you have your entire ‘web’ directory structure which has css, js, WEB-INF/* like structure in your workspace, you no longer need to manually deploy or run an ant task to copy your classes. Any jsp changes or controller classes will automatically be detected and redeployed if necessary