+1 On Mon, Nov 3, 2008 at 7:18 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote: > Hey, > > 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). > > /Rickard > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev >
-- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
