For resin-managed database pools or other shared resources/beans, polluting 
resin/lib with non-resin libraries can be avoided by adding a class-loader 
section to the top of resin.conf and defining a tree loader path or, if you 
want to explicitly iterate every include, a library loader path for every jar.


-----Original Message-----
[] On Behalf Of Shane Cruz
Sent: Thursday, June 25, 2009 10:24 AM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Sometimes resin can find jdbc driver in webapp, 
other times no. What gives?

If you define your database pools at the server level in resin.conf,
then you need to put the JDBC drivers in the resin/lib directory so the
pools can be created when the server starts.
Privileged/Confidential Information may be contained in this message. If you 
are not the addressee indicated in this message (or responsible for delivery of 
the message to such person), you may not copy or deliver this message to 
anyone. In such case, you should destroy this message and kindly notify the 
sender by reply email. Please advise immediately if you or your employer does 
not consent to Internet email for messages of this kind. Opinions, conclusions 
and other information in this message that do not relate to the official 
business of my firm shall be understood as neither given nor endorsed by it.

resin-interest mailing list

resin-interest mailing list

Reply via email to