Hi!
> |Yes, that is also true. I will shortly add a ServiceControl that will be
> |able to start/stop the services in the order they were registered (i.e.
> |the infamous jboss.conf order). This will, at least in the short term,
> |make the DependencyManager deprecated.
>
> wait a second, the dependency manager is a bit deeper than that. We need
a
> dependency tree, not just a "order" on startup. Sure the linear order
will
> do the trick for the startup sequence but the dependency service build
trees
> of dependency not just linear structures.
>
> Set >> Tree >> LinkedList
>
> For the use we do of it I agree that both are equivalent, but for the
grand
> dream of "the service goes down, all dependent services (parents)" are
> notified, the "tree service" needs to exists.
>
> But don't worry, we will cross that bridge when we cross that bridge, I am
> just raising a flag on removing that...
I know, and I agree. But for now people just aren't using that tree, so it
became not very interesting.
That said, the tree dependency can still be done later on. This is just
functionality on top, which does not require changes to the services
(provided they "play nice").
One step at a time though, and I think this will address the ease-of-use
complaints with jboss.conf+jboss.jcml, and a bit more.
regards,
Rickard
