[
https://issues.apache.org/jira/browse/MYFACES-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631771#action_12631771
]
Matthias Weßendorf commented on MYFACES-1902:
---------------------------------------------
So? Even if JBoss EL is not compatible, why should myfaces not allow a hook?
That doesn't mean we should use J Boss EL as default. This would have two major
problems:
-we can't use JBoss stuff @Apache, b/c of license
-if it is really incompatible, we don't pass the TCK
However, if customers want to use it in myfaces instead of the "original" one,
why not?`
> Allow to use different ExpressionFactory implementation
> -------------------------------------------------------
>
> Key: MYFACES-1902
> URL: https://issues.apache.org/jira/browse/MYFACES-1902
> Project: MyFaces Core
> Issue Type: New Feature
> Components: Extension Feature
> Affects Versions: 1.2.4-SNAPSHOT
> Reporter: Christian Kaltepoth
> Assignee: Matthias Weßendorf
>
> It should be possible to use a different ExpressionFactory implementation.
> This feature is required
> to use 3rd party EL implementations like JBoss EL. Mojarra already supports
> this with the
> 'com.sun.faces.expressionFactory' context parameter.
> MyFaces Core 1.2.x already supports a context parameter
> 'org.apache.myfaces.EXPRESSION_FACTORY'
> but it is only evaluated in a JSP 2.0 environment (see MYFACES-1693 for
> details).
> It should be possible to use this parameter with JSP 2.1 as well. The
> corresponding code
> should be refactored from Jsp20FacesInitializer to AbstractFacesInitializer
> to be usable in both
> JSP 2.0 and 2.1.
> Discussion on myfaces-users:
> http://www.nabble.com/Replacing-expression-factory-td18867420.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
