Something I've done on a project is write a class that handles some of
the things that change from one environment to another. This class
actually delegates to another object whose classname can be configured
via property file. The upshot is that my code asks this thing for a
connection to 'SQLServerPool'. We'd have two delegates: one using a
home-grown connection pool, the other using JNDI to get the connection
(just tacking java:comp/env/jdbc onto the front of the requested pool name).
That might be overkill for what you want, but on the other hand, unit
tests (like with JUnit) are very important.
-danch
Alan McDade wrote:
> No, I need to write JSP's with, depending on the scope of the project,
> either direct JDBC connection or EJB's. However for testing the effect of
> classes on the database non-server client would have been less work.
>
> Never mind what will be will be!
>
> Thanx for the advice
>
> Alan
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of danch (Dan
> Christopherson)
> Sent: 20 June 2001 21:44
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] Cannot connect to java:/SQLServerPool
>
>
> Yes. If all you need is connection pooling for a standalone application,
> I believe there are open source pool drivers out there.
>
> -danch
>
> Alan McDade wrote:
>
>
>> Does this mean I can only use the DataSource from within a
>> Servlet/JSP/EJB????
>>
>> Alan
>>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
