I was just thinking, waiting for tests to complete (they take hours to hit the error scenerio)... and while I wait I get back to the meaningful work.
So, It occured to me that the <classpath> element really does not do too much except deploy urls for archives which it has found, or has an explicit list of. So why isn't this just another MBean? I certainly don't wan't ClassPathExtention to come back to life, but I think that we could add a much better service which will do the same job as <classpath> (perhaps more)... and as MBeans go if it doesn't do what you need, then you plug in a different version. Then we could move JARDeployer into jboss-service.xml, right before the classpath service which setups all of the UCL's to the lib/* stuff. I think I am probably missing something... like that before we start calling service methods we must register every MBean with the server... I don't know that is the case... but if it is, I suggest that is not optimal. Anyone know what the case is here? --jason _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
