The value is simply in tge fact tgst it's explicitly nullable. Thst matters in a post-JSR-303 world. It removes ambiguity. On Dec 9, 2012 11:28 AM, "Matt Benson" <[email protected]> wrote:
> My position is that the absence of @NotNull implies "Nullable." I don't > see the value of an explicit annotation. > > Matt > > > On Sun, Dec 9, 2012 at 9:19 AM, Carlos Vara <[email protected]> wrote: > >> Hi Matthew, >> >> Unless I'm missing something, I think @Nullable would just be a no-op for >> validation purposes. My view on the issue would be to instead allow JSR-303 >> validators to perform runtime validation of JSR-305/Findbugs annotations, >> where @Nullable is already available. >> >> >> >> On Tue, Dec 4, 2012 at 11:23 AM, Matthew Adams >> <[email protected]>wrote: >> >>> Hi all, >>> >>> *NB: Cross posting from the Hibernate Validator forum, since this is >>> spec-related, not implementation related. HV forum post is at >>> https://forum.hibernate.org/viewtopic.php?f=9&t=1024895.* >>> >>> I just entered https://hibernate.onjira.com/browse/BVAL-341 (the >>> JSR-303 issue tracker, I think) since I was curious as to what other folks >>> thought about adding a @Nullable annotation to javax.validation.constraints >>> to communicate explicitly that null or non-null values are allowed. Along >>> with @NotNull & @Null, it basically completes the three possible answers to >>> the nullability question, "can't be null", "must be null", & "may be null". >>> >>> Thoughts? Upvotes? :) >>> >>> -matthew >>> >>> >>> -- >>> mailto:[email protected] <[email protected]> >>> skype:matthewadams12 >>> googletalk:[email protected] >>> http://matthewadams.me >>> http://www.linkedin.com/in/matthewadams >>> >>> >> >
