[
https://issues.apache.org/jira/browse/MYFACES-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835895#action_12835895
]
Jan-Kees van Andel commented on MYFACES-2565:
---------------------------------------------
I put it there when implementing the first version of BeanValidator. The spec
says the following:
http://java.sun.com/javaee/javaserverfaces/2.0/docs/api/javax/faces/validator/BeanValidator.html#validate%28javax.faces.context.FacesContext,%20javax.faces.component.UIComponent,%20java.lang.Object%29
Let valueExpression be the return from calling
UIComponent.getValueExpression(java.lang.String) on the argument component,
passing the literal string "value" (without the quotes) as an argument. If this
application is running in an environment with a Unified EL Implementation for
Java EE6 or later, obtain the ValueReference from valueExpression and let
valueBaseClase be the return from calling ValueReference.getBase() and
valueProperty be the return from calling ValueReference.getProperty(). If an
earlier version of the Unified EL is present, use the appropriate methods to
inspect valueExpression and derive values for valueBaseClass and valueProperty.
Back then, it was not possible to completely implement this method, because
Unified EL was not available, so I put the TODO and Exception in. I assume we
can now safely implement the remaining part.
> 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
>
> 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.
