According to the JMX spec there is a "Relationship Server" for JMX Agents
and I think this is the service we should implement in our JMX Agent.
I will go (again) over the JMX spec and see what we can gain from the
JMX Agent Relationship Service and then try to make a proposal for
a full fledged JMX Agent within jBoss (yeah, after I finish the first
version of the JMX Connector).
But as far as I have in mind is that the spec isn't very specific and
as the most of you know JMX spec is still in beta (for a long time)
and I don't think this will change in the near future. Therefore we
have to do it by ourselves which give us another opportunity to be
ahead the others.
Have fun
Mad Andy
> -----Original Message-----
> From: Juha Lindfors [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 30, 2000 1:09 PM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] JMX Status?
>
>
> At 20:40 30.8.2000 +0200, you wrote:
> >You are absolutely correct, with the additional requirement
> that it is
> >not registration that is really important, but that the
> MBean has been
> >started (i.e. init+start).
> >
> >Also, this should not be handled by the service itself, but by some
> >third party "relationship handler". This makes the MBeans themselves
> >much simpler and less reliant on each other I think.
>
> I think the typical solution for servers with pluggable
> components is to
> provide a single bootstrap service ("relationship handler")
> and then an
> event bus that all the other components register to and send their
> notifications. Then the other components can listen to the
> bus to know when
> another component comes "online" or ask for the bootstrap
> service (upon
> their own registration) if their requierd components are
> already available.
>
> Was that the kind of thing you were talking about?
>
>
> -- Juha
>
>
>
