On Aug 5, 2008, at 4:52 PM, Paul Smith wrote:
I really really really dislike this change.
Errors are not designed for use by programs but by the jvm itself.
I prefer if this change was reverted and the use of a wrapping
runtimeexception instead.
I was trying to preserve the external behavior that would occur with
the old code if you did not provide jmxtools.jar at runtime. As
implemented, both the new code and the old code would result in a
NoClassDefFoundError if it was deployed without jmxtools.jar.
However, the likelihood that some client code out there has something
like:
try {
new Agent().start();
} catch (NoClassDefFoundError ex) {
}
is vanishingly small, so switching to a RuntimeException is not a big
issue to me. I'd prefer not to revert the whole change, but to
change the Error constructors to RuntimeException constructors which
I'll do and see what you think.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
