Sorry forgot to say this is on JBoss 3.2.1
I have fixed the unregistration of the driver
at undeploy, however I can't get redeploy of
Driver classes to work.
There is some horrible class caching somewhere
in java.sql.Driver, it looks like a horrible attempt
at security for applets judging by the hint
in the javadocs.
Do you know if the Driver instance was garbage collected between your deployments?
Is it possible that the static initialisation is not being called the second time the class is loaded?
The Driver instance is garbage collected.
The driver is re-registered with the DriverManager,
but it doesn't use it.
It says "skipping" if I set the logWriter to System.out,
it seems to be caching the original class or classloader
somewhere then saying I cannot use the driver
because I would load a different class for the driver.
Just wanted to check to see if you have made any further progress on this issue?
Should this be logged as a bug at sourceforge so it can be tracked?