Hi!
"Patrick J. McNerthney" wrote:
> Personally, I don't like the fact that jboss is rewriting my
> jboss.jcml. I prefer to always start from a *known* configuration and
> not have to worry about my configuration files being rewritten with more
> information than I put in them. Yes, it is *suppose* to rewrite it with
> the correct information, but I just don't like messing with anything in
> a working environment. Now, every time I take jboss down and start it
> up again, it is not running in *EXACTLY* the same environment that it
> last ran in. It is running with the jboss.jcml file that it created
> during the last run, which will not be 100% guaranteed to be the same.
>
> I just ran into another issue with regards to the rewritten jboss.jcml.
> I archived up my working jboss installation and sent it to a co-worker
> to get working on their system. Everything would have worked fine,
> except for the fact that the rewritten jboss.jcml had some file path's
> from my system written into it. I had to find the original, *clean*
> jboss.jcml that I created before I every ran jboss the first time and
> send that one along.
>
> I would prefer a new file to be created, instead of overwriting the
> original jboss.jcml. Call it jboss.jcml.complete, or something. Just
> don't go messing with the configuration files that I have carefully
> crafted into nudging jboss to do it's magic!
I understand your point, but the .jcml is supposed to reflect the
current state of jBoss and the only way to do that is to rewrite it
after applying it to the server. If there are some settings like file
paths that are expanded, that is a bug I think, and should be fixed. It
is absolutely necessary that this is done, since when jBoss is running
and some setting is changed (e.g. through the admin interface) the .jcml
file should be updated to reflect this new setting so that it is used
the next time the server is started.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
