I am managing the database connection credentials because this is the only
way to access this legacy database. Otherwise I have very little code
because Hibernate takes care of all the heavy lifting. As part of the
deployment I just need a way of defining the datasource in a manner that is
external to my code and configurable by administrators. I am trying JNDI as
my standard because this has various levels of security of db uid/pw from
web server to web server. If I fallback to using spring/hibernate xml to
configure the datasource then my customers will always have to decide if
they can live with the uid/pw being stored in a clear text xml file before
taking my app.
-- 
View this message in context: 
http://www.nabble.com/How-to-turn-off-JNDI-datasource-connection-pooling-tp21490681p21507739.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to