I'd recommend using the bit mechanic pool manager (or even better, Orion's
own pooling). PoolMan does bad things with the classpath in order to work
with tomcat's broken classloading. It tries to look many of its classes
through the system classloader.
On Mon, 6 Aug 2001, Ismael wrote:
> Trying to use PoolMan as connection pool I get some errors.
> When Poolman tries to load its xml configuration file it fails warning that
> org.apache.xerces.parsers.SAXParser class is not found.
> I have put xerces.jar and PoolMan.jar on the
> ../applications/myapp/web-app/WEB-INF/lib folder.
>
> I have tested it with Orion 1.4.5 and it works fine, then we think that
> there is something wrong with Orion 1.5.2.
>
> Regards,
> Ismael
>
>
>
