myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Andraschko (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Resolved] (MYFACES-4151) When @FacesConfig is not present, EL resolution in managed beans should not be performed
Date Sat, 09 Sep 2017 08:22:00 GMT

     [ https://issues.apache.org/jira/browse/MYFACES-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Andraschko resolved MYFACES-4151.
----------------------------------------
    Resolution: Fixed
      Assignee: Thomas Andraschko

> When @FacesConfig is not present, EL resolution in managed beans should not be performed

> -----------------------------------------------------------------------------------------
>
>                 Key: MYFACES-4151
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4151
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.3.0-beta
>            Reporter: Eduardo Breijo
>            Assignee: Thomas Andraschko
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> According to the JSF 2.3 spec section 5.6.3 "CDI for EL Resolution" - When @FacesConfig
annotation is present in any of the managed beans, the ImplicitObjectELResolver is not present
in the chain, instead CDI is used to perform EL resolution. However, when @FacesConfig is
not present, we are still using CDI to perform EL resolution in the managed beans. 
> On Mojarra, app does not start, throwing DeploymentExceptions similar to this: 
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies
for type FacesContext with qualifiers @Default
>   at injection point [BackedAnnotatedField] @Inject private com.ibm.ws.jsf23.fat.beans.TestBean.facesContext
>   at com.ibm.ws.jsf23.fat.beans.TestBean.facesContext(TestBean.java:0)



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

Mime
View raw message