XOM API for Processing XML with Java

["Trimmer, Todd" <todd.trimmer AT trizetto.com>]

Default ctors for Exceptions might be used for serialization or JavaBean
introspection related technology. I cannot cite any specific examples of why
someone would want to serialize an Exception, either by itself, or as part
of an aggregate that wants to serialize. Nor can I cite a good use case for
mingling Exceptions with introspection. I am personally in favor of removing
no-arg ctors. I just wanted to bring those two things up so maybe it will
make light bulbs go off in someone else's head about something important.

A question to ask would be, "Should ALL implementations/subclasses of
Throwable/Exception lack a no-arg ctor?" If yes, then we should have no
qualms about removing them from XOM.

Exception doesn't have a setMessage(String) method, so it's not like some
sort of scripting technology that bridges to Java can more easily create
Exceptions by doing the object creation and setting its values in two
distinct steps. So why bother with a no-arg ctor at all?



Todd Trimmer