On Wed, 2012-01-11 at 05:01 -0800, Thom Hehl wrote: > We are using a context configuration file to provide our database > connectivity through a JNDI entry to our application so that the file > can change without the purchasers of our software having to tinker about > with it internally. Here is our file: > > > > <Context path="/chronicle" debug="5" reloadable="true" > crossContext="true"> > > > > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="ej-Log." suffix=".txt" timestamp="true"/> > > <Resource name="jdbc/chronicle" > > > auth="Container" > > type="javax.sql.DataSource" > > username="sa" > > password="xxxxxxx" > > > driverClassName="net.sourceforge.jtds.jdbc.Driver" > > > url="jdbc:jtds:sqlserver://localhost/PsDb" > > > maxActive="-1" > > > maxIdle="0" > > /> > > </Context> > > > > I picked this trick up from a predecessor on a job and have never found > it documented anywhere.
I'm not exactly sure what you mean here, but JNDI (i.e. the <Resource/> tag) is document here. https://tomcat.apache.org/tomcat-7.0-doc/jndi-resources-howto.html and here. https://tomcat.apache.org/tomcat-7.0-doc/config/globalresources.html > I would like to use the same approach to define > JNDI keys for the mail server. Can someone help? You can certainly do this. Here's a link to the docs which describes how to define Mail Sessions. https://tomcat.apache.org/tomcat-7.0-doc/jndi-resources-howto.html#JavaMail_Sessions Dan
