> 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.
I would estimate that about 95% of the cases where users want to add their
own services they would add them to the place in jboss.jcml that says "Place
your custom MBeans here". I.e. last. For the other 5% I'm not worried. It's
not that difficult, really.
> 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.
Alright, noted.
> 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.
As above, I have a slightly shorter instruction: "put all custom MBeans
last. Done".
To me that is a big improvement over "first put an entry into jboss.conf,
although you have to look in the source to figure out what constructors are
available, then add settings to jboss.jcml, and if it depends on something
go edit jboss.dependencies too. Oh, and it doesn't work at runtime, only at
startup."
Just IMHO of course.
/Rickard
