[
https://issues.apache.org/jira/browse/MYFACES-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan-Kees van Andel resolved MYFACES-2565.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-beta-3
It should work now, however I don't like the implementation. I need to resort
to reflection if I want to use the ValueExpression.getValueReference() method,
because the compile classpath contains two entries for ValueExpression: One in
jsp-api-2.1 and one in el-api-2.2.
Someone please review the implementation...
> 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.
