Absolutely.
The only reason why I can think that @NotNull makes sense is when you
want to have access to the default values of attributes of these not
null elements. For the other cases, an optional injection coupled with
if (!=null) is much better.
jerome
On 6/16/10 8:21 PM, Bill Shannon wrote:
> I'm only barely following this thread, but...
>
> Rather than adding @NotNull all over the place until everything works,
> wouldn't it be better in most situations to change the code to tolerate
> null/missing elements?
>
> I'm sure it's easier to just sprinkle in @NotNull until it works, but
> is that really the right solution in all cases?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>