Return-Path: X-Original-To: apmail-bval-user-archive@www.apache.org Delivered-To: apmail-bval-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB2E195FE for ; Sun, 9 Dec 2012 15:19:31 +0000 (UTC) Received: (qmail 36547 invoked by uid 500); 9 Dec 2012 15:19:31 -0000 Delivered-To: apmail-bval-user-archive@bval.apache.org Received: (qmail 36467 invoked by uid 500); 9 Dec 2012 15:19:30 -0000 Mailing-List: contact user-help@bval.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@bval.apache.org Delivered-To: mailing list user@bval.apache.org Received: (qmail 36430 invoked by uid 99); 9 Dec 2012 15:19:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Dec 2012 15:19:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bashflyng@gmail.com designates 209.85.215.175 as permitted sender) Received: from [209.85.215.175] (HELO mail-ea0-f175.google.com) (209.85.215.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Dec 2012 15:19:23 +0000 Received: by mail-ea0-f175.google.com with SMTP id h11so792300eaa.34 for ; Sun, 09 Dec 2012 07:19:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XUiFBBCR6gaEl7t22U5aP5khSku1AJ5AyQ1SSHm5Re4=; b=ccJS2LKgtLDvH4GuZnql7nqeWYb9kXVUiQOu+gNnQW8DcCKY5p8AJXYb2h52b6qn3o b1ZRQSSMRmxLiALUhLST7Yia7qLsRxvE4unegT5WYb2bFq0Ovkygq0jDm1NY5Y7GjF9w GypfNDoHSCwddkpzakDPIfXE+LWl1GCJUCkqgPkhRsByPNSacvb5+bJdLRTghEK/IMYK N0dvCYPd+uPuq6S51IcxWVGjI8IWToulJ6gYUh/jnYh3i6X1buvjD9g31beBcriSBJNo 5hZmLe/YO2Sn1ayA3S9YcAbSKoG4mtzA941IaQLA2um5WpXkc7gn+auf+9fRc+dpUeGq Utww== MIME-Version: 1.0 Received: by 10.14.219.3 with SMTP id l3mr39373542eep.5.1355066343142; Sun, 09 Dec 2012 07:19:03 -0800 (PST) Received: by 10.223.86.73 with HTTP; Sun, 9 Dec 2012 07:19:03 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Dec 2012 07:19:03 -0800 Message-ID: Subject: Re: Thoughts on @Nullable? From: Carlos Vara To: user@bval.apache.org Content-Type: multipart/alternative; boundary=047d7b621b9007b4c204d06cf84d X-Virus-Checked: Checked by ClamAV on apache.org --047d7b621b9007b4c204d06cf84d Content-Type: text/plain; charset=ISO-8859-1 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 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:matthew@matthewadams.me > skype:matthewadams12 > googletalk:matthew@matthewadams.me > http://matthewadams.me > http://www.linkedin.com/in/matthewadams > > --047d7b621b9007b4c204d06cf84d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Matthew,

Unless I'm missing something, I think @N= ullable 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 <matthew@matthewada= ms.me> wrote:
Hi all,

NB: = =A0Cross posting from the Hibernate Validator forum, since this is spec-rel= ated, not implementation related. =A0HV forum post is at https://forum.hibernate.org/viewtopic.php?f=3D9&t=3D1024895.

I just entered https://hibernate.onjira.com/browse/BVAL= -341 (the JSR-303 issue tracker, I think) since I was curious as to wha= t other folks thought about adding a @Nullable annotation to javax.validati= on.constraints to communicate explicitly that null or non-null values are a= llowed. Along with @NotNull & @Null, it basically completes the three p= ossible answers to the nullability question, "can't be null",= "must be null", & "may be null".

Thoughts? Upvotes? :)

-matthew

= --
mailto:matthew= @matthewadams.me=A0
skype:matthewadams12
googletalk:matthew@matthewadams.me
http://matthewadams.me
http://= www.linkedin.com/in/matthewadams


--047d7b621b9007b4c204d06cf84d--