[ https://issues.apache.org/jira/browse/MYFACES-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonardo Uribe reopened MYFACES-2565: ------------------------------------- The patch committed here causes MYFACES-2605. It was added these dependencies: <dependency> <groupId>javax.validation</groupId> <artifactId>validation-api</artifactId> <version>1.0.CR3</version> <optional>true</optional> </dependency> <dependency> <groupId>javax.el</groupId> <artifactId>el-api</artifactId> <version>2.1.2-b05</version> <optional>true</optional> </dependency> That's not good. The el-api dependency version should be 1.0, so we can't use code in a upper version. > BeanValidator throws Exception if external ExpressionLanguageFactory is being > used > ---------------------------------------------------------------------------------- > > Key: MYFACES-2565 > URL: https://issues.apache.org/jira/browse/MYFACES-2565 > Project: MyFaces Core > Issue Type: Bug > Affects Versions: 2.0.0-beta > Reporter: Mark Struberg > Assignee: Jan-Kees van Andel > Fix For: 2.0.0-beta-3 > > > Currently the BeanValidator has the following code: > if (_ExternalSpecifications.isUnifiedELAvailable()) > { > //TODO: Implement when Unified EL for Java EE6 is available. > throw new FacesException("Unified EL for Java EE6 support is not yet > implemented"); > } > I'm using EL-2.2 in MyFaces-2.0.0-SNAPSHOT and now switched from using > facelets-1.1.15.B1 to the built-in facelets-2. > After that I get this rather unfunny Exception in the code above. > I tried to remove this condition in BeanValidator and so far all works well. > Afaik the new EL-2.1 interface should be backward compatible to the EL of > JSF-2.1, isn't? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.