I just read the Java Management Extensions (JMX) spec. Here's a quote from
it:
"JMX provides a standard way to enable manageability for any Java based
application, service or device. For example, Enterprise JavaBeans� (EJB)
applications can conform to the JMX architecture to become manageable."
I wonder how people see JMX and EJBs fitting together. I'm not writing an
EJB container, just EJBs. Since the life of an EJB is controlled by its
container, I think only notifications from EJBs to a JMX server would be
possible. Calls from a JMX server into an EJB don't make much sense. Maybe
the advantage of using JMX might be at deployment time with a custom
deployment tool that uses JMX?
Dave
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
