Hi!
marc fleury wrote:
> Why the different files, can't we extend the MLET XML file to include the
> stuff we are looking for for each component? Under each MLET have the tag
> <conf> contain the stuff you use. I know we do the stuff for the ejb
> configurations and that there the recommendation was to separate the files
> since the target audience was separate but in our case it seems it will be
> the same person that deals with the file.
Yes, but the MLet conf file is defined in the JMX spec. Same thing
really; I don't want to mess with defined formats (besides, the MLet
implementation seems really cranky about it. You can't even add <!-- -->
comments..).
Also, it is a good thing to have initialization and configuration
separately. There could be several configuration utilities (XML configs,
serialization configs, database configs, etc.) so having them too tight
together is not good IMHO. Componentization. Modularization. It might
not seem logical right now, but I think we will "phew" sometime down the
road. Just a hunch ;-)
> > The only drawback is that the order of the MBeans as specified in the
> > MLet text file cannot be determined after they have been loaded. Because
> > of this they may be initialized in one order (the order that they appear
> > in the MLet text file), but be configured and started in another (the
> > order they are represented in the MBeanServer, typically based on hash
> > indexes). Because of this, some services which rely on others to be
> > started (e.g. DataSource needs Naming to be started in order to use JNDI
> > properly) will fail. The temporary workaround is to do start() logic
>
> Ah yes... well I mentioned that at the expert meeting as a need for jboss
> (from some of the mails we exchanged) and I must admit I think it drew blank
> stares... Maybe I explained it poorly.
Duh, I had this stuff in XS years ago when I was a uni kid 8-) I would
*hope* that the /relation package in the latest JMX API is for this
purpose.
If it is not, it is possible to add these kind of dependency stuff
ourselves. One thing I did in XS was to make these dependencies like a
tree where the top node was "Da Server". So, when I started the server
everything else was started automatically through the dependency chain.
Really cool. And if some node would fail, the others depending on it
would not start. And so forth.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
