On 11/01/2012 13:01, 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:

Which version of Tomcat is this?

Which file is this?


p

> <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 would like to use the same approach to define
> JNDI keys for the mail server. Can someone help?
> 
>  
> 
> Thanks.
> 
>  
> 
> 


-- 

[key:62590808]

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to