"[EMAIL PROTECTED]" wrote : I don't like the <classpath/> configuration in -service.xml Does not liking it mean: a) it should not be used because it is unreliable and things break, or b) we should really change the whole implementation in this area because it is not very nice, or c) all of the above, or d) none of the above
I have done some simple tests with the alternative deployment scenario: ./deploy/my-datasource-service.xml (including classpath element pointing to mydriver.jar) | ./data/datasource_drivers/mydriver.jar and other than the locking of mydriver.jar which Dimitris points out, it seems to "work". Where "work" means: -you can hot deploy a datasource. -you can update the -service.xml to point to a different driver and after JBoss restarts the datasource will use the new driver. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863795#3863795 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863795 ------------------------------------------------------- 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 JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
