It is a problem to me as it just compounds startup and shutdown times. If I read the spec correctly, every jndi ref, url ref, resource ref, etc has a mangement object. There is no need to create an explicit MBean for every logic object.
I think there should MBeans for the coarse level objects like deployments and services, but when it gets down to a JNDIResource, or a URLResource, why do I need an MBean as opposed to an attribute on the owning MBean? xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Sacha Labourey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 16, 2003 10:03 AM Subject: RE: [JBoss-dev] JSR-77 refactoring has begun > > I agree that if you take the spec and literally create a MBean > > for every management > > object there will be an absurd number of MBeans. So what does this super > > MBean look like? > > Is that really a problem? What if the overhead of an MBean? If that is > really a problem because the "routing" logic of the MBeanServer will take > too much gime, why not simply create a second MBeanServer, just for JSR-77 > purposes? ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
