On Tue, Nov 4, 2008 at 02:18, Rickard Öberg <[EMAIL PROTECTED]> wrote: > Just checking, should I go ahead and implement @Optional? I.e. assume > that all method parameters are non-null by default (and throw NPE if > they are null), and then allow setting @Optional as an annotation if the > value can be null. This would remove the @NotNull constraint in the > process, which seems like a good thing (as it is used almost everywhere > now). +1
Regards, Edward Yakop _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
