Yeah, and like Gareth said, it's pretty easy to make a mock jndi
container for your tests.
Larry
On 1/5/07, Wesley Wannemacher <[EMAIL PROTECTED]> wrote:
>
>
> There's one additional advantage to using JNDI for this ...
> in many shops
> you have two or even three environments to worry about
On 1/5/07, Christopher Schultz <[EMAIL PROTECTED] > wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wesley,
(Sorry, I accidentally sent my previous message before I was finished
writing).
Wesley Wannemacher wrote:
> The main reason that I am currently leaning toward the iBATIS solution
>
>
>
> There's one additional advantage to using JNDI for this ...
> in many shops
> you have two or even three environments to worry about (development,
> staging, production), each with its own database instance. Having the
> database configuration for each instance in its own server
> mean
On 1/5/07, Christopher Schultz <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wesley,
Wesley Wannemacher wrote:
> When configuring the database connections, where do you tend to put
> them?
Without question: have your container create the connection pool and
make it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wesley,
(Sorry, I accidentally sent my previous message before I was finished
writing).
Wesley Wannemacher wrote:
> The main reason that I am currently leaning toward the iBATIS solution
> is that I am finding jUnit tests difficult to write for my pe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wesley,
Wesley Wannemacher wrote:
> When configuring the database connections, where do you tend to put
> them?
Without question: have your container create the connection pool and
make it available via JNDI. This is the most portable configuration y
> -Original Message-
> From: Gareth Evans [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 05, 2007 11:39 AM
> To: Struts Users Mailing List
> Subject: Re: [FRIDAY] DBCP configuration
>
> Hi,
>
> I had a very similar problem using hibernate and a jndi
Hi,
I had a very similar problem using hibernate and a jndi datasource, the way I got around this for
unit testing was to create the jndi datasource within my unittest setup method, it's a little messy
but works for me (tihs class also loads the spring configuration files too):
import java.ut
8 matches
Mail list logo
