I'd be glad to use the DeploymentInfo if an MBean had access to it. The startService() method has no parameters. The MBean only has access to the primitive values initialized from its XML attributes. So how would the MBean get a hold of it?
I do not understand why you feel that having a ClassLoader for the MBean would fail to solve my problem. Shouldn't the ClassLoader, in conjunction with the njar protocol, be able to resolve a relative "file:" protocol address within an archive to a fully explicit "njar:" URL that could be used to create an InputStream [ClassLoader.get*Resource*() methods]. Please explain. And don't worry, I won't be making changes unless a senior developer says go. I am definitely the new kid on the block and nervous about modifying anything. My contribution was going to be to JBoss.net. On the other hand, we have to deliver an application and I'm trying to figure out how to make it work. Fred. At 07:46 AM 5/20/2002, you wrote: >Please do not bring back a classloader/mbean. I don't think it will do >what you want anyway. > >What is wrong with using the DeploymentInfo for the package that has the >info you want in it? DeploymentInfo already has a reference to the >classloader that loads everything in that package. > >david jencks > >On 2002.05.20 01:33:13 -0400 Frederick N. Brier wrote: > > I just backtracked through the source, and read a bunch of messages of > > Mark > > Fleury, Scott Stark, and David Jencks. It sounded like Scott was saying > > in > > February (17th) that all the MBean(s) are using the same ClassLoader. > > But > > Mark and David were discussing in April ClassLoader(s) per MBean. So I > > am > > not sure where this all stands. It looks like the code is in place to > > allow any MBean to have its own classloader [MBeanServerImpl: invoke(), > > line 481]. It appears that an MBean ClassLoader must itself be an MBean > > and registered. If all this is working and I just don't understand how > > the > > <classpath> element works, let me know. On the other hand, David just > > told > > me that I can't use a ClassLoader to find a resource. > > > > It would appear that all that needs to happen is that the SARDeployer > > create a ClassLoader MBean based on the DeploymentInfo/Inflated file > > system > > location and the <classpath> element, and insert it at the beginning of > > the > > list of MBeans found in the jboss-service.xml file fed to the Service* > > classes in the org.jboss.system package. Then specify the ClassLoader > > MBean's ObjectName when invoking the MBeanServer.createMBean() method. > > The > > ServiceCreator.install() method actually makes the call to the > > MBeanServer > > to create the MBean [line 104-108], but has the parameter for the named > > ClassLoader commented out. > > > > This stuff is very intertwined. And I am not entirely sure that even if > > I've grasped it, I should attempt to complete the author's intent. But > > if > > y'all say go ahead, I'll give it a whirl, unless someone else is willing > > to > > step into the breach. Please give me some feedback. Thank you in > > advance. > > > > Fred. > > > > > > _______________________________________________________________ > > Hundreds of nodes, one monster rendering program. > > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > >_______________________________________________________________ >Hundreds of nodes, one monster rendering program. >Now that's a super model! Visit http://clustering.foundries.sf.net/ > >_______________________________________________ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
