On Wed, Oct 10, 2012 at 07:46:28PM +0200, helix84 wrote:
> On Wed, Oct 10, 2012 at 6:40 PM, Mark H. Wood <[email protected]> wrote:
> > It's also missing from dspace.cfg.
> >
> > Should I correct these omissions?  Is the JNDI code stable enough to
> > expose?  I've used it in testing without incident, but not yet in
> > production.
> 
> Hi Mark,
> 
> sorry for the stupid question, but what is it good for?

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.

If db.jndi is not defined or doesn't resolve, DSpace falls back to
building its own pool.

One thing this lets you do is privilege separation: the person
installing DSpace doesn't need to know the credentials for the DBMS.
The DBA and the person who administers the container are the only ones
who need to know.  We don't do that here, but I like the idea of
moving out of dspace.cfg things that don't really have to do with how
DSpace operates.

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.

-- 
Mark H. Wood, Lead System Programmer   [email protected]
Asking whether markets are efficient is like asking whether people are smart.

Attachment: pgp9C1XnWy6wN.pgp
Description: PGP signature

------------------------------------------------------------------------------
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

Reply via email to