This is an old FAQ. JDBC drivers CANNOT be hot deployed, or more accuratly redeployed.
The class java.sql.DriverManager does some horrible classloader caching. If you change Sun's class to use the thread context classloader rather than Class.forName() then it becomes possible to redeploy jdbc driver classes. The only workaround is to redeploy JBoss's local jdbc resource adapter when you want to redeploy a driver (which doesn't work very well if there is no more than driver). I don't see the need to add <classpath/> tag to the -ds.xml since you get much better semantics by creating a sar that contains both the -ds.xml and the driver jar. But still no hotredeploy. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862469#3862469 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862469 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
