Eddie, I just read your post and hope you didn't misunderstand me...
I wasn't saying that you shouldn't use JNDI to get a reference to the DataSource. I was simply saying that you should do it only once, not every time you need it. Yaakov. -----Original Message----- From: Eddie Bush [mailto:[EMAIL PROTECTED] Sent: Friday, January 28, 2005 3:32 PM To: Struts Users Mailing List Subject: Re: Database Connection Workflow Question Jack, Would you *please* post URLs instead of full source? I know you have publicly-hittable space of your own ... So far as how to acquire a DataSource/Connection goes, JNDI is a fantastic tool for allowing your persistence layer acquire a DataSource instance in a *standard* fashion. Standards aren't always "best practice" approaches, but getting DataSource instances from JNDI is a best practice. ... although I do like the idea of caching the DataSource instance, as mentioned earlier, in a private member of some class in your persistence layer. -- Eddie Bush --------------------------------------------------------------------- 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]
