Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (athena.apache.org: domain of gturner@unzane.com designates
 184.105.220.20 as permitted sender)
From: Gerald Turner <gturner@unzane.com>
To: "MyFaces Discussion" <users@myfaces.apache.org>
Subject: Re: ExtVal BV question
References: <87d38pi9wt.fsf@zoth-ommog.unzane.com>
	<87vcmhgngf.fsf@zoth-ommog.unzane.com>
	<CAL+wt-6=+Xh1fS=ecZKoXNPy9X=Wb43haRM3LvLLeP5180ufAQ@mail.gmail.com>
Date: Thu, 08 Mar 2012 11:50:29 -0800
In-Reply-To: 
 <CAL+wt-6=+Xh1fS=ecZKoXNPy9X=Wb43haRM3LvLLeP5180ufAQ@mail.gmail.com>
	(Rudy De Busscher's message of "Wed, 7 Mar 2012 09:44:22 +0100")
Message-ID: <87ipiehny2.fsf@zoth-ommog.unzane.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Rudy De Busscher <rdebusscher@gmail.com> writes:
> first, welcome to the mailing list.

Thanks!

> a) about the multifield ConstraintValidator.
> You see the messages twice since you set 2 ConstraintViolation on the
> context.  And to my knowledge there is no link between the
> propertyPath and the component the message is intended to.  Not in the
> JSR303 and thus not in the ExtVal support for it.  Can you please
> point us to the info (spec) if we are wrong.

In JSR303 =C2=A7 4.2 ConstraintViolation, there is the following note:

  =E2=80=9CFrom rootBean and propertyPath, it is possible to rebuild the
   context of the failure=E2=80=9D

The chapter continues with several examples of these Node/Path objects.

Unfortunately the specification doesn't make any further statements
about how JSF or any other toolkits *should* infer what components are
in violation, but the spec is framework agnostic afterall=E2=80=A6

> b) Validation in 2 phases
> This is due to the fact that you need all the field values in the
> model before you can do any multifield validation.
>
> Within the Process Validation phase, the JSF validations on a single
> field takes place (required, within limits, etc ...). ExtVal then also
> processes the BeanValidation annotations which are placed on the
> field/method like @Size, @NotNull etc ...
>
> But the multi field validation can't be performed at that moment
> because it requires that the screen values are propagated to the
> managedBean.  This is because the ConstraintValidator needs the object
> populated with the values to do his checks.  This means it can be only
> done after the 'update model values' phase and thus only performed
> when no problems are found yet.
>
> Hopes this clarifies the things a bit.

Yes this makes sense, I just wanted to clarify I wasn't doing something
wrong, missing configuration, etc.  I think it is acceptible for the
user interface that the more complex validations happen in a second
pass.

=2D-=20
Gerald Turner   Email: gturner@unzane.com   JID: gturner@unzane.com
GPG: 0xFA8CD6D5  21D9 B2E8 7FE7 F19E 5F7D  4D0C 3FA0 810F FA8C D6D5

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk9ZDYUACgkQP6CBD/qM1tWivgCgkk8qYP4NmV6HYhtGrMbQ5UL7
hW4Anj83yVz11xY1I36Zdj3T1zJeHapG
=nuOs
-----END PGP SIGNATURE-----
--=-=-=--