When I use a jboss.jcml file with invalid parameters, then the
rewritten jcml file leaves a couple parameters out. In my case, it's
JDBCUser and TimestampUsed, not URL, so who knows what it depends on. I
think there's definitely a JMX bug at the heart of this, since as Oleg
points out the JMX MBeanInfo reports that the relevant attributes are not
writeable.
So, the big question is where we go from here. If the problem is
*only* caused by invalid parameters in jboss.jcml, we could just trap that
and System.exit after printing any appropriate error messages. But I'm
not sure this is the case. Another option would be to ignore the
writeable flag, since we ignore any parameters we don't set - but it may
be a little weird to see a bunch of "StateString" parameters show up all
of a sudden.
Hmmm... I think what I'll try is to dig out the MBean class and
check the writeability manually instead of depending on JMX. That may be
the best option.
Aaron
