..is almost done. I need to make sure everything works as expected.
There was a lot of breakage during this development, and currently I'm
having some strange problems with the EmbeddedTomcat service. Weird as
hell.
Anyway, here's the deal:
jboss.conf now only contains core services. What's needed to get things
going. This includes the logging and classpathextension MBeans.
After that is done the jboss.jcml (which contains user conf, and is not
overwritten automatically) is read, and all MBeans in it are
instantiated and registered in the server. Then the settings in
jboss-auto are applied, without creating any MBeans that was not created
by loading jboss.jcml. This allows services to be removed in jboss.jcml
without breaking things (i.e. having them be re-created by
jboss-auto.jcml). Lastly jboss.jcml *settings* are applied to the
MBeans, overwriting any that was auto-saved. If you want to be able to
do admin changes through tools and have them persist a restart, then
simply don't add any attribute settings in jboss.jcml. That way only the
jboss-auto.jcml settings are used.
After that the MBeans are called on "init" method *in the order they
were specified in jboss.jcml*.
After that the MBeans are called on "start" method *in the order they
were specified in jboss.jcml*.
Then server is successfully started.
That was that. Works well, except for the above mentioned.
So, now one only has to deal with jboss.jcml when adding new services.
Oh, and I think I've fixed the "found JMX bug" problem which corrupts
the autosaved jcml file.
Oh, and I've broken out the shutdown hook into a separate MBean so that
a) one can skip it on JDK 1.2.2 JVMs
b) one can call "shutdown" through remote admin interface and have the
server be shutdown cleanly. Neat
Almost done. But the day is over, so gotta go. Will fix the last pieces
and commit tomorrow. If you have any objections to the above workings..
well, too late 8-)
I think it will work out just great. :-)
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
