I reported the problem below as a bug at http://bugs.caucho.com/view.php?id=5587 which was marked as fixed to version 4.0.40
The release notes for 4.0.40 says "bind java:comp/BeanValidation (#5587)" and I can confirm in the code that the JNDI name in use indeed is java:comp/BeanValidation, rather than java:comp/ValidatorFactory Problem is, AFAI can see this does not solve the original issue. When replacing javax.faces-2.1.24.jar with jsf-api-2.2.5.jar + jsf-impl-2.2.5.jar bean validation does not work. I still have to configure java:comp/ValidatorFactory within our application. (Googling "java:comp/BeanValidation" only has 1 hit: the Resin 4.0.40 release notes mentioned above, so where does that even come from...?) Should I create a new issue, or will http://bugs.caucho.com/view.php?id=5587 be reopened? For the record, seems that Mojarra 2.2.7 will take care of container backwards compatibility https://java.net/jira/browse/JAVASERVERFACES-3183 </Mattias> > Resin ships with Hibernate Validator. I'm trying to figure out whose > responsibility is it to make the ValidatorFactory exposed in JNDI as > java:comp/ValidatorFactory. > > What we are really trying to do is using JSF 2.2 with Resin, and then Bean > Validation is disabled since JSF is unable to find the factory at > java:comp/ValidatorFactory (where JSF 2.1 explicitly called > Validation.buildDefaultValidatorFactory()). > > Seems to work fine using JBoss. So is this a bug with Resin, that > java:comp/Validator and java:comp/ValidatorFactory are not available by > default...? _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
