myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] Commented: (MYFACES-1902) Allow to use different ExpressionFactory implementation
Date Wed, 17 Sep 2008 05:29:46 GMT


Leonardo Uribe commented on MYFACES-1902:

Checking the documentation of jboss el here

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:
>             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
> '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:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message