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
> -----Original Message-----
> From: Scott M Stark [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 06, 2001 10:58 AM
> To: JBossDev
> Subject: Re: Deployment Dependencies (was RE: [JBoss-dev] RH
> startup and
> J Boss MQ)
>
>
> This is really an implementation detail of adding
> <depends>xxx</depends>
> element.
> What is the difference between having a depends attribute or element?
>
> ----- Original Message -----
> From: "David Jencks" <[EMAIL PROTECTED]>
> To: "David Maplesden" <[EMAIL PROTECTED]>
> Cc: "JBossDev" <[EMAIL PROTECTED]>
> Sent: Wednesday, September 05, 2001 3:24 PM
> Subject: Re: Deployment Dependencies (was RE: [JBoss-dev] RH
> startup and J
> Boss MQ)
>
>
> > Hi,
> >
> > I don't have a very good feeling about having 2 kinds of
> dependency tree
> in
> > the same file - the classpath one and the one you are proposing.
> >
> > Another approach that is used by the jca stuff and has been
> requested
> > recently for the j2eedeployer is to use NotificationBroadcaster.
> >
> > 1. ServiceDeployer broadcasts notifications each time it
> deploys/undeploys
> > a sar/jar/service.xml
> >
> > 2. If you have a dependency to a mbean in another package,
> you write your
> > mbean to check for the object name when it is initialized,
> and to register
> > for notifications. Whenever it gets a notification, it can
> check for
> > deploy/undeploy of what it is looking for and go to an
> appropriate state.
> >
> >
> > This should be pretty easy to code into ServiceMBeanSupport or a
> descendant
> > so all you have to do is supply the object names you are
> looking for --
> > this could even be an attribute in the service.xml file.
> >
> > what do you think?
> >
> > thanks
> > david jencks
> >
> >
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
