On 2002.03.02 14:51:08 -0500 marc fleury wrote: > |for it using depends. Marc wanted to use the MBeanClassLoader to keep > |track of class dependencies and wait if a class was not found when you > |tried to "install" it. I'm not sure how far he got with this. > > Yes that was its purpose before the advent of the Unified ClassLoader > everywhere. > > That will actually simplify the dependency tracking tremendously so we > wont > need it. > > As we discussed in Boston David, the dependency tracking through explicit > depends at the MBean name level with *anything* is the way to go. Can we > support that yet?
I made a little progress;-) Ejbs and ejb modules (representing ejb-jar packages) are now mbeans participating in service lifecycle management, so mbeans configured from service.xml files can depend on them. resource adapters already were mbeans. sar/bare service.xml packages, ears and wars are not yet represented by mbeans. There is not yet a way to make an "ejb mbean" (the Container) or an Ejb Module mbean depend on anything simply because there is syntactically nowhere to write the dependency. This could be in jboss.xml pretty easily. To make an (ear) application depend on something we'd need a jboss-application.xml. I haven't had a chance to work on the xml transformation stuff yet. Do you think it or the new jca connection manager framework is more important? This works great for object instances (actual mbeans) but I don't see how it applies to the "where is my class" issue. david jencks > > marcf > > > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
