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!

Thanks again for the AWESOME work,

Pat McNerthney
Icicle Software, Inc.


Aaron Mulder wrote:
> 
>         Okay, once again, I believe I've fixed the problem that causes
> URLs to disappear from jboss.jcml.  It's in CVS, as of moments ago.  As
> Oleg indicated, the JMX RI reports certain attributes as read-only when
> they're really not.  I finally managed to duplicate it, though strangely
> for different attributes.
>         Anyway, we just worked around the problem by checking the
> attribute writeability manually instead of asking JMX.  Though I still
> can't nail down the exact circumstances that cause the problem, hopefully
> that will fix it for everyone.
>         There will be a new binary build soon, for those that don't want
> to mess with CVS.
> 
> Aaron

Reply via email to