Using PoolMan with Tomcat 3.2.1

[Barney Hamish <Ha...@ect-telecoms.de>]

Has anyone out there been able to get PoolMan 2.0.4 to work with Tomcat
3.2.1 realm based authenitcation?

I'm currently using PoolMan 2.0.4 with Tomcat 3.2.1. The problem arises when
I try to use the PoolMan driver with the JDBC Realms.

The PoolMan driver requires one to register the driver by calling:
class.forName("com.codestudio.sql.PoolMan").newInstance();

However the Tomcat JDBC Realm only calls :
class.forName(XXXX);  (org\apache\tomcat\request\JDBCRealm.java line 425)
Without the calling the newInstance() method.

As a result the driver is not registered and when the JDBC Realm interceptor
attempts to connect to the database a SQL 'No suitable driver' Exception is
thrown.

I was wondering if any of you have been able to get PoolMan and Tomcat
Realms to play together nicely. Obviously I could create a custom build of
Tomcat that would call the newInstance() method but I would rather work with
a standard version of tomcat. Is anyone aware of a way I can perhaps get
tomcat to register the driver _before_ tomcat tries to setup realms?

Thanks for you help,
Hamish