You might want to take this question to the user- list as well. RU does makes extensive use of the JNDI configs for database pools for other applications, but we could live with the change you are proposing.
Bill On 10/8/07, Eric Dalquist <[EMAIL PROTECTED]> wrote: > Anyone have any thoughts on this? > > If I don't hear any reasons to keep the JNDI configs as the default way > of doing things I'll be changing trunk to use commons-pool managed > DataSources in the portal's application context. > > -Eric > > Eric Dalquist wrote: > > The issue of where to put those darn JDBC drivers has come up a few > > times in the last week or so on the -user list and has historically been > > a bit of an issue. > > > > I would like to propose no longer using a JNDI configured DataSource by > > default. With the consolidated Spring configuration I would like to > > create a dataSourceContext.xml as a place to configure JDBC DataSource > > objects. RDBMServices would be deprecated and re-worked to provide > > access to the DataSource objects from the Spring context. As work > > progresses to move more components into a Spring managed world they > > could bypass RDBMServices and simply have the DataSource injected directly. > > > > -Eric > > > > -- William G. Thompson, Jr. Associate Director - Architecture & Engineering Enterprise Systems and Services, Rutgers University voice: 732 445-5428 | fax: 732 445-5493 | [EMAIL PROTECTED] -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
