Not a problem :-)
Note, this is a bug in the DriverManager. Basically what is going on is some heinous
cacheing of classes that prevents the class from being loaded. Supposedly this is
addressed in JDBC 4.0. Also, the Class.forName("classname") mess goes away. The
DriverManager will be able to load the classes automatically without the registration
process.
Regards.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975921#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...