The reason to use the server.xml file is so Tomcat controls the pooling mechanism. If you want it in your web.xml (webapp) then you want the app to control it. JNDI is app-server, no reason to have your webapp maintain a JNDI context... just embed poolman into your webapp.
Really, the mechanism described for pooling with JNDI is intended to allow your webapp to run in many different locations, with the same war, and allow the app-server to configure what database/pooling (size, etc) so they become deployment changes, not changes that require a new webapp. If that's not an issue for you, then just use poolman. > This one time, at band camp, Neil Aggarwal said: > > NA>I am trying to set up JNDI and pooling with Tomcat 4. > NA>According to the instructions on this page: > NA>http://castor.exolab.org/pooling.html > NA> > NA>I have to put my database info in the global server.xml file > NA>for Tomcat. This is not desirable since we have many projects > NA>and would like everything modularized. > NA> > NA>Since the database is specific to my web application, is there > NA>a way to put it only local to the application? For example, > NA>only in the web.xml file? -- Virtually, Ned Wolpert <[EMAIL PROTECTED]> 4e75 ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
