On Wed, Oct 10, 2012 at 9:31 PM, Mark H. Wood <[email protected]> wrote: > If the property is defined, the DBMS code will look it up in JNDI and > use the value of that (if found) as the connection pool. Many servlet > containers (following the JEE spec, where this is standardized) > provide a JNDI InitialContext which can be loaded with such objects at > startup, or you can build a pool and serialize it to an LDAP directory > for lookup.
I see, once I was trying to configure the DB pool as a Resource in the Tomcat Context. But it didn't work. So I guess the reason was that I didn't have db.jndi defined. But what would the value of db.jndi be? > I have some code which will do the same thing with the email > properties, replacing them with looking up a preconfigured Session. > It was too late for 3.0 but I will propose it again for 4.0. That sounds great! Thanks for the explanation. Regards, ~~helix84 ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
