Return-Path: X-Original-To: apmail-openjpa-users-archive@minotaur.apache.org Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E152E108BD for ; Wed, 2 Oct 2013 17:22:02 +0000 (UTC) Received: (qmail 52923 invoked by uid 500); 2 Oct 2013 17:22:02 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 52632 invoked by uid 500); 2 Oct 2013 17:21:59 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 52623 invoked by uid 99); 2 Oct 2013 17:21:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 17:21:58 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of allee8285@gmail.com does not designate 216.139.250.139 as permitted sender) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 17:21:52 +0000 Received: from jim.nabble.com ([192.168.236.80]) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VRQ6k-0005rA-IU for users@openjpa.apache.org; Wed, 02 Oct 2013 10:21:06 -0700 Date: Wed, 2 Oct 2013 10:20:51 -0700 (PDT) From: allee8285 To: users@openjpa.apache.org Message-ID: <1380734451533-7585025.post@n2.nabble.com> In-Reply-To: <1380662073777-7585013.post@n2.nabble.com> References: <1380662073777-7585013.post@n2.nabble.com> Subject: Re: Bean validation on merge? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org For "Automatic Validation upon Lifecycle Events" (see JPA 3.6.1.2), the Validator.validate() will be called on em.flush or tx.commit. Per BVal spec 3.5, all "reachable" fields will be validated. Therefore merge, or any other em operations, has no bearing on how the validation will take place. To control any subset of fields to be validated, use group definition and the javax.persistence.validation.group.* property to specify your customize validation scheme. Albert Lee. -- View this message in context: http://openjpa.208410.n2.nabble.com/Bean-validation-on-merge-tp7585013p7585025.html Sent from the OpenJPA Users mailing list archive at Nabble.com.