|I agree with you and think that this will be a source for
|a log of email in jBoss-User.
|I think that when we separate stuff it will be much better
|maintanable than bring all in one (not everyone is a Guru).
well the dependency is not going to be the major problem (few people are
going to change that and we can really document the pool one)....
the problem is that most stuff doesn't work right now, period :( testbeans
doesn't deploy from Deployer /doesn't run and most importantly it breaks the
previous jboss.xml jrmp settings... pffff.....
i'll stick by the kid on this one, but Rickard, clean it up man, it's
sloppy!
marc
|
|Have fun - Andy
|
|-----Original Message-----
|From: Aaron Mulder [mailto:[EMAIL PROTECTED]]
|Sent: Thursday, December 07, 2000 8:28 AM
|To: jBoss Developer
|Subject: Re: [jBoss-Dev] New configuration scheme
|
|
|On Thu, 7 Dec 2000, Rickard �berg wrote:
|> 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.
|
| You're missing a couple points here. First, with the current
|system one doesn't need to worry about where they put an entry in a config
|file. I suspect most casual jBoss users who hear "add XXX to jboss.jcml"
|do not understand what other services "XXX" depends on, and what other
|services depend on it.
| Now, it's true that the dependency manager currently handles
|startup only. But it would be trivial to change it to either produce a
|properly ordered list of services, or perform initialization as well as
|startup/shutdown.
| As for runtime starting and stopping, I think the solution is to
|implement that not ignore it. Again, it's not a difficult change for the
|dependency manager - all the logic is in place.
| So, whether the DM is ultimately ever used again or not, I think
|your new approach is definitely a step back.
|
|Aaron
|
|P.S. "Put the DB pool in the file, but after the logging and TM and before
|the auto deployer and J2EE deployer. And probably before the servlet
|engines, and after naming and hypersonic and instantDB, and after the JDBC
|driver loader and JNDI, but before Castor and JAAS and the container
|factory." Yeah, what an improvement.
|
|
|
