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
