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 (development, > staging, production), each with its own database instance. Having the > database configuration for each instance in its own server > means you do not > need to go tweak your connection parameters as you move your > app from one > place to another. > Thanks Craig and Christopher, you have convinced me. In my attempts to make my life easier, I was definitely forgetting about SysAdmins... As this app moves through its various stages, it probably would be best to allow Operations to configure the database connections using methods they are already familiar with. Thanks for the input and you probably saved me some grief as this gets passed on. -Wes --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
