[ https://issues.apache.org/jira/browse/MYFACES-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Nicolucci resolved MYFACES-4503. ------------------------------------- Resolution: Fixed > TCK: Application.getExpressionFactory should return > ELManager.getExpressionFactory() > ------------------------------------------------------------------------------------ > > Key: MYFACES-4503 > URL: https://issues.apache.org/jira/browse/MYFACES-4503 > Project: MyFaces Core > Issue Type: Bug > Components: General > Affects Versions: 4.0.0-RC2 > Reporter: Paul Nicolucci > Assignee: Paul Nicolucci > Priority: Major > Fix For: 4.0.0-RC3 > > > [Application.getExpressionFactory() > |https://jakarta.ee/specifications/faces/4.0/apidocs/jakarta/faces/application/application#getExpressionFactory()] > states the following for Faces 4.0: > {noformat} > The implementation must return the ExpressionFactory from the Expression > Language container by calling jakarta.el.ELManager.getExpressionFactory(). > {noformat} > Previous to Faces 4.0, for instance, Faces 3.0 the same > [Application.getExpressionFactory() > |https://jakarta.ee/specifications/faces/3.0/apidocs/jakarta/faces/application/application#getExpressionFactory()]states > the following: > {noformat} > The implementation must return the ExpressionFactory from the Jakarta Server > Pages container by calling > > JspFactory.getDefaultFactory().getJspApplicationContext(servletContext).getExpressionFactory(). > {noformat} > Currently, for Faces 4.0 our behavior is incorrect and it needs to be changed > to leverage the ELManager API. > For reference, there is a [TCK > Challenge|https://github.com/jakartaee/faces/issues/1718] relating to this > behavior. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)