> Right then, I guess you can try placing the driver
> class in the WEB-INF/lib or APP-INF/lib directory as
> well as leaving it on the system or application
> classpath.
>
> In case this is some sort of odd classloading bug
> occuring on your OS I would try exploding the jar
> file and try adding the directory structure to your
> classpath or WEB-INF/classes etc.
>
> Hoos
I don't think this is an issue with the classloader not finding the driver. From the output, it appears that when Weblogic tries to generate the Proxy Class, the classpath at that point is () or empty. I base that on the debug output from the class loaders