I'm not sure I understand. The fundamental problem is that once a class looks up a jdbc driver java.sql.Driver remembers the classloader where the driver was found.
If the driver gets redeployed java.sql.Driver will effectively say the driver is not in the place I expected (it cached the info) and ignore it when checking what drivers are visible. The code is actually intended to stop java applets looking at each other's drivers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864140#3864140 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864140 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
