On Thu, 30 Nov 2000, Rickard �berg wrote:
> The motivation for writing the jcml file has been discussed a number of
> times (see archives), and will not be changed. What will be changed is
> the buggy behaviour by some of the MBeans that makes the file corrupted.
>
> /Rickard
Well... I have to agree with numerous other posters that the
existing behavior is pretty irritating. And I particularly like the idea
of writing any runtime changes to another file and thne using that file
during startup if it's present (so you can just delete it to ignore the
changes), or something like that.
However, the disappearing DB settings now seems to be caused only
by serious configuration errors - like you try to load a DB pool but don't
have the right classes in your classpath. I tried to work around this
(see all the additional junk in setURL and getURL in XADataSourceLoader)
and that still doesn't cut it - so I think maybe some calls are causing
the MBean to crap out before all the settings have been set or something,
and thne when you go to write it again it just has no idea what the unset
fields should be.
Perhaps we chould change this so the MBean just stores all the
settings and doesn't try to apply any until you call start... Or perhaps
we just shouldn't rewrite the config file if any MBeans failed to
load/start.
Aaron
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
