I am a bit at loss with what @Nullable will be useful for in the 303 world. Literally the constraint validator will simply return true every single time. I understand the usefulness of @Nullable for static code analysis - whether it be done by a compiler, tool or a human. But what would @Nullable offer in the "dynamic" land of JSR 303?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Hello Matthew,
I am a bit at loss with what @Nullable will be useful for in the 303 world. Literally the constraint validator will simply return true every single time. I understand the usefulness of @Nullable for static code analysis - whether it be done by a compiler, tool or a human. But what would @Nullable offer in the "dynamic" land of JSR 303?