Re: [Treebase-devel] Switching to JNDI Datasource

[Vladimir G. <vla...@du...>]

The main reason is switching to JNDI.  This will factor DB credentials  
(url, username, password) out of the WAR, allowing us to easily deploy  
(and redeploy) multiple instances of the application.

As per my recent problem with the unit tests, I've now got a tip from  
Youjun on how to proceed, so I hope the two of us will be able to  
resolve this.

--Vladimir


On Jan 12, 2010, at 3:21 PM, Hilmar Lapp wrote:

>
> On Jan 12, 2010, at 3:19 PM, William Piel wrote:
>
>>
>> On Jan 12, 2010, at 3:10 PM, Vladimir Gapeyev wrote:
>>
>>> Youjun has noted that the JNDI update will break the tests
>>
>> Is there a big advantage to switching from the mchange connection
>> pooling package to commons-dbcp ?  (meaning, despite being
>> "obscure," if it works, is now the right time to switch this, given
>> that we're in the final stretch for a TreeBASE release?)
>
> Bill - that's a good point, though switching or not switching the
> connection pooling implementation won't affect or help with the JNDI
> setup for unit tests.
>
> 	-hilmar
> -- 
> ===========================================================
> : Hilmar Lapp  -:- Durham, NC -:- informatics.nescent.org :
> ===========================================================
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast  
> and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Treebase-devel mailing list
> Tre...@li...
> https://lists.sourceforge.net/lists/listinfo/treebase-devel