Commons Lang's Validate.notNull() throws NPEs. I don't know that I've
necessarily agreed with that, but at some point a decision was made
that null constraint violations should throw NPEs. Food for thought.
On Fri, Aug 30, 2013 at 8:32 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
> On Fri, Aug 30, 2013 at 8:25 AM, Emmanuel Bourg <ebo...@apache.org> wrote:
>
>>
>> >> + if (parameter == null) {
>> >> + throw new IllegalArgumentException("Parameter '" +
>> parameterName + "' must not be null!");
>> >> + }
>> >> + }
>> >> +}
>>
>> Isn't a null value supposed to throw a NPE ?
>>
>
> Not always IMO. When I see an NPE I assume something is very wrong and that
> it could be a bug in the impl OR a call site, somewhere on the code path.
>
> With an IAE, I know for sure it's a problem in the call site (which could
> be a bug of course).
>
> I does not help that the JRE/JDK is inconsistent, so it's hard to find
> examples.
>
> Gary
>
>
>> Emmanuel Bourg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second
> Edition<http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
