No, the best way to add an mbean for your ejb is to include an mbean in your ear that has a dependency on the ejb. If you don't already have a doc subscription go and get one as it has a draft of the 3.0 admin and devel manual that talks about the JBoss mbean extension that supports a richer service lifecycle including dependency management. I'll add an example of a dynamic mbean associated with an ejb in the next draft.
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 9:40 AM Subject: Re: [JBoss-user] MBean interfaces to EJBs > Let me add, that I figured the best way to do this would be to listen > for Deployment Notifications, then I would be able to look up the newly > registered ObjectNames for the deployed EJB's. This would allow me to > determine the JNDI name, get a copy of its Local Interface and invoke > methods based on deployment and undeployment. But as I noted in a > previous email Deployment Notifications occur prior to actual deployment > so queryNames returns no results, and therefore this approach isn't > feasible either (without modifying JBoss). > > It would be better to be able to implement the postRegister methods as I > mention below. > > Mike ------------------------------------------------------- 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
