Hello Chris > This is an apt analogy. The server.xml sets up the actual resource > (often in the <GlobalNamingResources> section), then allows the > application to use it (by adding a <ResourceLink> section in the > <Context> where you want to use it). The webapp signifies its desire to > use that resource by including a complimentary <resource-ref> section in > the deployment descriptor.
I'm out of my depths with JNDI, but am I right in presuming that a webapp cannot 'set up' a JNDI resource all of its own, in its deployment descriptor? IOW, only the container (Tomcat) can set up a JNDI resource, which its webapps are then able to use. Sorry if this is labouring the point. A simple 'yes/no' will suffice! Kind regards Harry Mantheakis London, UK --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
