On Thu, 10 Aug 2000 18:39:13 -0700, Dave Halbakken
<[EMAIL PROTECTED]> wrote:
>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?
There are two sides of the story here. First, there is the management of
how the *EJB container* runs the beans of the application. Second, there
is the management of *the application* itself. These are two entirely
different things. I think the quote you referred to was pointing to the
latter form of management, where you as a bean write provide an
MBeanServer implementation that delegates to your EJB's.
There was a session at this years J1 (from IBM I think) about a group
that hade made just this. Pretty cool. Search java.sun.com/javaone for
details.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
===========================================================================
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".
