On Tue, May 22, 2012 at 10:52:31PM -0700, Mark Diggory wrote: > If we were to just use spring and abandon the dspace configuration > approach, we could implement the selection of the appropriate DAO as a > choice between spring xml files placed into dspace/config/spring/...
While doing that, I would be grateful if we can preserve the ability to provide a preconfigured DataSource out of JNDI, ignoring DSpace's DBMS configuration (if any). I'm using that here to provide a distinct database connection setup for one of the commandline tools that has fits with Commons DBCP here and really shouldn't be using pooling anyway. (Does anyone run DSpace in a servlet container which does *not* provide some sort of JNDI context? Tomcat and Jetty both do. Any JEE container MUST. Maybe we can push the choice out of DSpace altogether. DataSource.getConnection().getDatabaseMetaData().getDatabaseProductName() will tell you which DBMS you are dealing with. That rids us of several of the very few bits of configuration data which *cannot* live inside of the DBMS. Maybe 2-3 context parameters/system properties would suffice for the rest.) -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgpFnzxhS45BT.pgp
Description: PGP signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
