"Eric Pugh" <[EMAIL PROTECTED]> writes:
>Getting a nice exception immediatly tells me that I misconfigured
>something.. Maybe teh ConfigurationFactory was wrong, or something else..
>And I know where to go to fix it. getting a NPE doesn't help so much...
I understand this. However, from an users point of view, using a
pre-1.0 release for a number of years (!) and then suddently getting
an exception from a code part that has never thrown an exception
before (but is reported to return null if the property does not
exist), will annoy users, that simply exchange a
commons-configuration-<some random snapshot> jar for the
commons-configuration-1.0.jar. Getting these exceptions from released
jars like the turbine-2.3 or torque-3.1 will not help, either. :-)
Hibernate e.g. took the pragmatic approach. You have one method that
might return null ( Session.get(Class, Serializable) ) and another
that throws an exception if the requested object does not exist
(Session.find(Class, Serializable).
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honorable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
