Then override the name in preRegister. Having to specify a name in the mbean service descriptor does not prevent this does it?
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Michael Stanley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 30, 2002 2:27 PM Subject: Re: [JBoss-user] MBean interfaces to EJBs > I'm currently building a system that requires plugins. > > We have a plugin development kit that allows developers to quickly write > plugins without having to worry about deployment configuration > information. The plugin developer simply implements the interface (or > subclasses some abstract support plugins). > > The plugin development kit, utlizing ANT, and Xdoclet, handles all the > EJB stuff, and EAR (or SAR) packaging. This alliviates a lot of the > details from the plugin developer. > > By removing the ObjectName from the configuration file, we can use a > generic MBean interface, that builds a unique ObjectName from some other > source (or combination there of, like plugin name, and version). > > This has multiple benefits. It allows the system administrator to set > up a domain specific to plugins (and change this easily over time), and > allows for a common naming convention to the generic PluginMBean (which > allows for common querying). > > Simply put, it seperates responsibilities of the developer, the > assembler, and the administrator. ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
