I'm sorry if I'm confusing the situation, I was just trying to describe the tests that I had done and why I persevered with this topic.
Fundamentally what I am trying to do is to find a way to manage datasources and drivers which has consistent and reasonable behavior. If that behavior includes needing to restart JBoss to see a change to a new driver then that is acceptable. What is less good is if the behavior includes exceptions being thrown in the server log and datasources being unavailable. For instance the testcase you described, JDBCStatementTestsConnectionUnitTestCase, indicates that hot redeploying drivers in JBoss will likely lead to class cast exceptions being thrown. Also in my tests, 1) above, I found that when redeploying a .sar file that contained a driver and datasource definition, that changing just the password attribute, caused references to the datasource to throw a NPE. The only scenario which appeared to show any promise was 3) from my previous post. Going forward I intend to follow a much more conservative approach to managing datasource and drivers. Namely putting drivers in ./lib, and -ds.xmls in./deploy. This will not give us the functionality we were hoping for from the Admin Console but I'm confident it will behave cleanly, e.g. not throw exceptions. I'm about to post a description of this new approach on the Admin console forum (http://www.jboss.com/index.html?module=bb&op=viewforum&f=209). If you are interested, your input would be valuable. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864146#3864146 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864146 ------------------------------------------------------- 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
