[
https://issues.apache.org/jira/browse/MYFACES-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838802#action_12838802
]
Jan-Kees van Andel commented on MYFACES-2565:
---------------------------------------------
Just looking at the JavaDocs of BeanValidator#validate(), it looks like a
null-check is missing.
"If ValueReference.getBase() return null, take no action and return."
I'll try to fix this issue (as well as the other BeanValidator related issues)
this weekend, but it depends, since I'm a bit behind schedule after JSFDays...
> 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.
