On 2001.09.06 09:58:31 -0400 marc fleury wrote:
> |Anyway the vote seems to be 1-all at the moment, anyone else? :)
>
> If you want to fight you take it outside. Anyway the optional
> <classpath>
> is there to express *class* dependencies, while the <depend> can express
> *MBean service* dependencies.
>
> In fact there could be cases where you could depend on an MBean and
> invoke
> it through the dynamicMBean interface and never need an interface hence
> never need a class. I think the <depend> stuff wins (by a small admin
> margin).
>
> David, you won
Well, now we can both get to work :-)
I think both are useful.
I'll put in one more plug for using notifications for <depends>
1. I think it would make resolving undeploy dependencies practical (maybe
even easy)
2. Non jboss mbeans with dependencies can be proxied or wrapped with a
dependency manager mbean.
thanks
david JENCKS
>
> marcf
>
>
>
> _______________________________________________
> 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
