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
