Hmm.... Relationships and dependencies ....
Are we thinking about managing dependencies between the individual services
only?, Are logical objects (groups of objects) catered for?
You may need a way to define groups of objects, and relationships between
groups and objects, rather than just relationships between objects.
Take an example of a naming service. You need AT LEAST one of them to be
working, but ideally you'd like 2 or 3. So you need somewhere to define
things like this. Whereby the application is working, even though some
components are not. In this case you can have a dependency on the Group of
naming services rather than an individual specific one.
Take the view of the systems admin person (a.k.a. SAP basis consultant) - he
doesnt know what JNDI is or care about a particular instance, all he knows
is that he needs to maintain a group and have at least one running inside
that group. Defining a "group" allows this. For true failover and management
of large deployments, stuff like this is needed.
-Rob
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Schaefer, Andreas
Sent: Thursday, August 31, 2000 7:01 AM
To: 'jBoss Developer'
Subject: RE: [jBoss-Dev] JMX Status?
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
>
>
>
