Berin Loritsch wrote:
I am adding some testcases to the merlin meta-api package. It is by no means
complete, but in the process I am cleaning some things up and strengthining
some contracts. The classes don't self validate much, although they do have
expectations that certain values are correct. As I go through, I am making
it fail early as opposed to later.
Quick question:
Is there any compelling reason to have both a declared exception and a runtime
exception for the meta-model? It seems to me a mixing of methodologies, so
I would like to standardize on one way of doing things.
The runtime exceptions are used in the meta builders.
There are some method implementations that will not throw an exception from a logical point of - ie - the sort of thing that you typically comment and say "this will never happen". Rather than swallow these exception cases I prefer to throw a runtime exception. Basically the usage of runtime exceptions indicates errors outside of the anticipated scope.
Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
