Let's not couple dependency management to JMX notifications.
----- Original Message -----
From: "David Maplesden" <[EMAIL PROTECTED]>
To: "'Scott M Stark'" <[EMAIL PROTECTED]>; "JBossDev"
<[EMAIL PROTECTED]>
Sent: Wednesday, September 05, 2001 3:59 PM
Subject: RE: Deployment Dependencies (was RE: [JBoss-dev] RH startup and J
Boss MQ)
> I think the argument is really about whether we list the dependents as
> mbeans or jsr/sar files.
>
> The problem with using Notifications is that it has to be coded into the
> mbeans themselves. Fine if people extend ServiceMBeanSupport and we can
> code it in there, but there is no requirement for mbean developers to
extend
> ServiceMBeanSupport and I feel we should have a mechanism to handle
> dependencies specified for any mbeans, not have to rely on mbean
developers.
> This does not mean that the Notifications are not a good thing to have,
they
> probably are, but I think we need another mechanism as well.
>
> So that leaves us with basically two proposals, use the archives listed in
> the classpath element as David Jencks suggests or list the dependent
mbeans
> explicitly in "depends" elements as I suggested.
>
> I actually think there is room for both mechanisms to a certain extent as
> there purpose is to achieve different things. David J's mechanism seems
to
> be aimed mainly at the automatic deploying and undeploying of an
application
> that is split across several jsr/sars while mine is mainly for
guaranteeing
> that all required services for an application exist before it is loaded.
>
> Anyway the vote seems to be 1-all at the moment, anyone else? :)
>
> David
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
