You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Eduardo Breijo (JIRA)" <de...@myfaces.apache.org> on 2017/07/27 20:04:00 UTC

[jira] [Comment Edited] (MYFACES-4129) When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't work

    [ https://issues.apache.org/jira/browse/MYFACES-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103813#comment-16103813 ] 

Eduardo Breijo edited comment on MYFACES-4129 at 7/27/17 8:03 PM:
------------------------------------------------------------------

I have provided a patch. You will notice that I added few more missing EL implicit objects. Any feedback will be appreciated.


was (Author: eduardobreijo):
I have provided a patch. You will noticed that I added few more missing EL implicit objects. Any feedback will be appreciated.

> When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't work
> ----------------------------------------------------------------------------------
>
>                 Key: MYFACES-4129
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4129
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.3.0-beta
>            Reporter: Eduardo Breijo
>         Attachments: ImplicitELObjects.war, MYFACES-4129.patch
>
>
> When the @javax.faces.annotation.FacesConfig annotation is used in a CDI bean, the implicit EL Objects from JSF 2.3 spec section 5.9.2 don't work. This is because when that FacesConfig annotation is in a bean we remove the implicit EL resolver from the chain so we don't have any mechanism for CDI to do the resolution of the implicit objects.
> Tested this on Mojarra and it works fine, with or without @FacesConfig annotation.
> A sample app is provided. It can be deployed on tomcat:
> 1) Drive a request to: http://localhost:8080/ImplicitELObjects/index.jsf
> 2) You should see that Application: ApplicationScope: and Component: are empty since they cannot be resolved



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)