I don't like the <classpath/> configuration in -service.xml 1) The semantics are not well defined. 2) Classloading dependencies are not defined at all in the current jmx kernel 3) There are some workarounds in the deployment code just to stop users trying to deploy the same jar twice through classpath elements in different -service.xml 4) The workaround in (3) does not take take into reference counting such that correct undeployment would work 5) It has no notion of LoaderRepository, i.e. what is the classloading domain and policy for these classloaders.
There is a ClassPathExtension MBean that can be used to add url classloaders to a loader repository and that MBean takes part in the service lifecycle. However, see (2) above. I need to be convinced that these scheme would work anyway, i.e. that you can actually redeploy a jdbc driver. e.g. "uncomment" the jdbc driver redeploy test in the jca part of the testsuite to see the problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863787#3863787 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863787 ------------------------------------------------------- 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
