<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Excellent.<div>I think that's good enough for the beta.</div><div><br></div><div>Here are the EE 6 requirements as outlined by the latest EE6 PFD (I've bolded what we need to work on still - AFAIK). I guess we should open JIRAs for that.</div><div><br></div><div><div>The Bean Validation specification defines a metadata model and API for JavaBean </div> <div>validation. The default metadata source is annotations, with the ability to override </div> <div>and extend the metadata through the use of XML validation descriptors. </div> <div>The Java EE platform requires that web containers make an instance of </div> <div>ValidatorFactory available to JSF implementations by storing it in a servlet </div> <div>context attribute named </div> <div>javax.faces.validator.beanValidator.ValidatorFactory. </div> <div>The Java EE platform also requires that an instance of ValidatorFactory be </div> <div>made available to JPA providers as a property in the map that is passed as the </div> <div>second argument to the </div> <div>createContainerEntityManagerFactory(PersistenceUnitInfo, Map) method of </div> <div>the PersistenceProvider interface, under the name </div> <div>javax.persistence.validation.factory.</div></div><div><br></div><div><div>Applications that need to use those interfaces can find appropriate objects by </div> <div>looking up the name <b>java:comp/Validator for Validator and java:comp/ </b></div> <div><b>ValidatorFactory for ValidatorFactory</b>, or by requesting the injection of an </div> <div>object of the appropriate type via the <b>@Resource annotation</b>. </div></div><div><br></div><div><br></div><div><div>A Validator or ValidatorFactory object reference may also be declared in a </div> <div>deployment descriptor in the same way as a resource environment reference. </div> <div>In order to customize the returned ValidatorFactory, an ejb, web or </div> <div>application client module may specify a Bean Validation XML deployment </div> <div>descriptor. <b>The name of the descriptor is WEB-INF/validation.xml for web </b></div> <div><b>modules, META-INF/validation.xml for all other types of modules. </b></div> <div><b>A validation deployment descriptor only affects ValidatorFactory instances </b></div> <div><b>in that module. </b></div> <div><b>There is no per-application validation deployment descriptor. </b></div><div><b><i>that's not implemented right? If someone can set up this per module separation, I can write the validation.xml parser in jboss-metadata and build the appropriate VF in the bv deployer</i></b></div> <br></div><div><br></div><div><br><div><div>On 15 sept. 09, at 19:20, Stan Silvert wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>I did a snapshot release of the BV deployers and integrated into Branch_5_x.<br><br>Current State of things:<br>* The BV Factory is created and added to the DeploymentUnit by the BV <br>deployer<br>* The BV Factory from the DeploymentUnit is added to application scope <br>for use by JSF. JSF/BV integration is working.<br>* The BV Factory is bound to global JNDI at <br>/BeanValidatorFactories/<DeploymentUnit.getSimpleName()><br><br>We know the JNDI part is wrong, so there will be changes. But hopefully <br>those of you waiting on this stuff can now make further progress.<br><br>Stan<br><br>Carlo de Wolf wrote:<br><blockquote type="cite">So these must be setup as LinkRefs by the container governing <br></blockquote><blockquote type="cite">java:comp to some other JNDI name which is bound by a deployer. Or <br></blockquote><blockquote type="cite">maybe we LinkRef to java:app/ValidatoryFactory depending on it's <br></blockquote><blockquote type="cite">scope. But at some point it will link to a 'global' name.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Carlo<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 09/15/2009 08:48 AM, Ales Justin wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">FYI wrt the JNDI names.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-------- Original Message --------<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Subject: [jsr-316-eg] Validator and validator factory names<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Date: Mon, 14 Sep 2009 17:25:58 -0700<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">From: Roberto Chinnici <<a href="mailto:Roberto.Chinnici@sun.com">Roberto.Chinnici@sun.com</a>><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Reply-To: <a href="mailto:jsr-316-eg@jcp.org">jsr-316-eg@jcp.org</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Organization: Sun Microsystems, Inc.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">To: Java Community Process JSR #316 Expert List <<a href="mailto:JSR-316-EG@jcp.org">JSR-316-EG@jcp.org</a>><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">As I was making a few editorial changes to the platform spec, I ran into<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">an actual mistake we need to fix for PFD.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Section EE.5.16 uses the following JNDI names for retrieving a validator<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">and a validator factory:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> java:comp/env/Validator<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> java:comp/env/ValidatorFactory<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">This seems wrong, because we typically reserve java:comp/env for<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">application-defined names.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">All other system-defined ones, like the ORB or UserTransaction, are<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">defined under java:comp.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">So I'm going to change the names above to the following ones:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> java:comp/Validator<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> java:comp/ValidatorFactory<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">My plan is still to submit the spec for PFD on Wednesday.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--Roberto<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><br><br>_______________________________________________<br>jboss-development mailing list<br><a href="mailto:jboss-development@lists.jboss.org">jboss-development@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/jboss-development<br></div></blockquote></div><br></div></body></html>