Yes it looks much much better :) a step in the right direction.
it is also true that the dependency stuff needed some "simplification" of
its own...
complicated code is the bane of humanity :)
regards
marc
----- Original Message -----
From: "Rickard �berg" <[EMAIL PROTECTED]>
To: "jBoss Developer" <[EMAIL PROTECTED]>
Sent: Thursday, December 07, 2000 6:50 AM
Subject: Re: [jBoss-Dev] New configuration scheme
Hi!
Aaron Mulder wrote:
> Hmmm... This sounds pretty complicated. Are normal human beings
> supposed to undertand this startup sequence, or are we planning to include
> some sort of tools to manage it?
Trust me, it is not complicated. It is much simpler than what is now.
Really. It may sound complicated, but 95% of the time all you have to
worry about is the jboss.jcml file and the attributes specified there.
> Also, may I object to starting things in the order they're listed
> in the file, instead of in an order consistent with their dependencies?
> You're ripping out advanced functionality and replacing it with a
> minimalist implementation, which doesn't seem particularly wise...
Are you talking about the dependency manager? Well, I looked at it, and
all it really is useful for is the startup sequence. But, for startup
all one needs is the *list* of services in the correct order, i.e.
jboss.jcml is enough. It is only necessary to use the dependencies for
start/stop at runtime. But, then I looked into DependencyManager, and it
didn't quite work. If a service is stopped, the dependent services
should also be stopped, but since the DM didn't listen for these events
nothing would happen. So, in its current form the DM is rather useless.
The stuff I'm about to commit will be sufficient for most uses, i.e.
start the server with the services in the proper order. For services
that wants proper runtime handling of start/stop, well that doesn't work
today either so it's not a step back.
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
