[
https://issues.apache.org/jira/browse/MYFACES-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839290#action_12839290
]
Jan-Kees van Andel commented on MYFACES-2565:
---------------------------------------------
Okay, but it's getting a bit nasty this way (copy-pasting this class 3 times,
especially since it is getting more complex).
I assume we also need to work with Java access permissions turned on?
Otherwise, we can do some reflection stuff, like:
- Putting all logic inside one class, let's say:
javax.faces.validate._ExternalSpecifications
- Putting some kind of bridge classes in other packages, like:
package javax.faces.component;
class _ExternalSpecificationsBridge {
public boolean isUnifiedELAvailable() {
try {
Class c = Class.forName("javax.faces.validate._ExternalSpecifications");
Method m = c.getMethod("isUnifiedELAvailable");
m.setAccessible(true);
return Boolean.TRUE.equals(m.invoke());
} catch () { return false; }
}
}
> 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.
