Defining JNDI DataSource...why decl'd/def'd in server.xml and not in web.xml.

I like to make my web applications and their corresponding installations/deployments as modular/atomic as possible. I like hot deployments, etc, etc. Unfortunately, every application I've seen that uses Tomcat JNDI DataSources requires hand-editing of server.xml...and then a reference to the

Re: Defining JNDI DataSource...why decl'd/def'd in server.xml and not in web.xml.

Mike, Why can't I describe the JNDI DataSource in the web.xml of my web application? I didn't notice this possibility in dtd for web.xml. That's because the application developers and server deployment team might be different people. It's much more natural to have the JNDI resources setup by