I did a snapshot release of the BV deployers and integrated into Branch_5_x.
Current State of things:
* The BV Factory is created and added to the DeploymentUnit by the BV
deployer
* The BV Factory from the DeploymentUnit is added to application scope
for use by JSF. JSF/BV integration is working.
* The BV Factory is bound to global JNDI at
/BeanValidatorFactories/<DeploymentUnit.getSimpleName()>
We know the JNDI part is wrong, so there will be changes. But hopefully
those of you waiting on this stuff can now make further progress.
Stan
Carlo de Wolf wrote:
So these must be setup as LinkRefs by the container governing
java:comp to some other JNDI name which is bound by a deployer. Or
maybe we LinkRef to java:app/ValidatoryFactory depending on it's
scope. But at some point it will link to a 'global' name.
Carlo
On 09/15/2009 08:48 AM, Ales Justin wrote:
> FYI wrt the JNDI names.
>
> -------- Original Message --------
> Subject: [jsr-316-eg] Validator and validator factory names
> Date: Mon, 14 Sep 2009 17:25:58 -0700
> From: Roberto Chinnici <Roberto.Chinnici(a)sun.com>
> Reply-To: jsr-316-eg(a)jcp.org
> Organization: Sun Microsystems, Inc.
> To: Java Community Process JSR #316 Expert List <JSR-316-EG(a)jcp.org>
>
> As I was making a few editorial changes to the platform spec, I ran into
> an actual mistake we need to fix for PFD.
>
> Section EE.5.16 uses the following JNDI names for retrieving a validator
> and a validator factory:
> java:comp/env/Validator
> java:comp/env/ValidatorFactory
>
> This seems wrong, because we typically reserve java:comp/env for
> application-defined names.
> All other system-defined ones, like the ORB or UserTransaction, are
> defined under java:comp.
>
> So I'm going to change the names above to the following ones:
> java:comp/Validator
> java:comp/ValidatorFactory
>
> My plan is still to submit the spec for PFD on Wednesday.
>
> --Roberto
>
>