Hi!
> Ok I understand we actually DON'T want people meddling with
jboss-auto.jcml
> (the source of our problems with jboss.jcml today) so serialization would
> buy that for sure, althought Dan and a few other mutants can read bytecode
> in the flesh. ("AE 8B 33 08 7F, ahah! you misconfigured your pool!")
True. However, during the upgrade I found it to be useful to start the
server with a minimal jboss.jcml, open up jboss-auto.jcml, and copy/paste
the settings into jboss.jcml and change to good defaults. For that kind of
stuff it is good to have it in XML.
> Now if you already have the XML read/write done then sure...
I do. It is in the Configuration MBean.
> xml is
> interesting at the tools/human interface (tools can parse and play with
it,
> humans can read and write it) but if it is a pure tools/tools play as in
> jboss.jcml then the overhead of parsing and XML'ing is useless.
But it's not much of an overhead, especially since it is dealt with
asynchronously. It can even be incremental, i.e. if an attribute changes
don't go ask every freakin' MBean about it's state just so we can write the
XML file. Today this is the case, but since the XML isn't updated on
attribute change, only at startup and manual invocation, it doesn't matter.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
