> Is this the same functionality your MBeanClassLoader > is supposed to > provide? If so, how exactly is this supposed to > work?
No it is not the same, it achieves the same but one is an administration *un-necessary* nightmare, the other one is implicit, you don't do anything. The presence of the list of jar is a hack to go around http lack of listing you have turned into the norm. This is why everyone is bombing with "file not found" btw the message is obscure now I will change it, > I think most of the problems are caused by the time > during which jetty > needed tools.jar in lib/ext and we couldn't ship it, > and the excessive list > in the conf/default/jboss-service.xml. IMHO these > jars need to be parceled > out to the packages that actually use them. No the problem is easily seen if you do a clean checkout and do a build core and run the stuff and the service.xml lists 1000 jars that we don't need. Look I think the MBean dependency and whether they boot or not is really the only thing I will tolerate specifying, we CAN'T track MBean dependency. (only relation service can) but we certainly can track classes that is what the MBeanClassLoader is there for. Do me a favor and trust me on simplicity of use, this is how 1.0, 2.0, 3.0 worked, this one file is a step backward. marcf ---- View: http://jboss.org/forums/thread.jsp?forum=66&thread=4932 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
