I browsed back through the latest spec and I am still not sure what some of these objects represent, but that is not important for my initial focus. What I want is to remove the dependency on JSR-77 components from the core layer. Right now even the minimal configuration has to include the
Beyond that, which management objects should or should not have MBean representations is up for debate and I'm not sure I care one way or the other in the absence of a prototype that indicates obvious advantages. Having a lot of objects is not in itself a very good reason to not use MBeans if there are overriding advantages. 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:43 AM Subject: RE: [JBoss-dev] JSR-77 refactoring has begun > Are you sure? I don't read the spec like that... As I understand it, you > don't need an MBean for every jndi ref, url ref, etc. but for every JNDI > service, etc. If you take a look at the EJBModule or EntitBean, I don't see > such a thing. ------------------------------------------------------- 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
