[
https://issues.apache.org/jira/browse/MYFACES-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631656#action_12631656
]
Leonardo Uribe commented on MYFACES-1902:
-----------------------------------------
Checking the documentation of jboss el here
http://docs.jboss.com/seam/latest/reference/en-US/html/elenhancements.html
it says that JBoss EL is incompatible with jsp 2.1, so enable this param in
this case is useless.
Is there another ExpressionFactory implementation available that gives some
features? if that so this issue has sense to be solved but if 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.
