Yes this behavior is intentional, so that Constraints don't need to worry about null at all. Cool, eh? ;-)
-- Niclas On 4 Dec 2009 03:00, "Stanislav Muhametsin" <[email protected]> wrote: While doing some minor tests with constraints, I noticed that if some method parameter is declared @Optional, and the parameter is null, any additional constraints that parameter might have, are not invoked. Example: void doSomething(@Optional @MyCustomConstraint parameter); If then parameter is null, the isValid method of the implementation of @MyCustomConstraint is never invoked. Is this because if parameter is null, no further constraint checking is deemed to be needed? Just wondering. :) _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
