myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Griffin (JIRA)" <>
Subject [jira] [Resolved] (PORTLETBRIDGE-224) Mojarra version dependency in JSF_ELTest for facesContext implicit object
Date Thu, 26 Jul 2012 18:44:35 GMT


Neil Griffin resolved PORTLETBRIDGE-224.

    Resolution: Not A Problem

MyFaces Portlet Bridge 2.0 has the following code in

      // Use one set as current instance in case we are wrapped
      mElContext.putContext(FacesContext.class, FacesContext.getCurrentInstance());

So I hereby retract this TCK Challenge since it's an issue that can be fixed in Liferay Faces
> Mojarra version dependency in JSF_ELTest for facesContext implicit object
> -------------------------------------------------------------------------
>                 Key: PORTLETBRIDGE-224
>                 URL:
>             Project: MyFaces Portlet Bridge
>          Issue Type: TCK Challenge
>          Components: TCK
>    Affects Versions: 2.0.0
>            Reporter: Neil Griffin
>            Assignee: Michael Freedman
> [Test Challenger Name and Company]
> Neil Griffin, Liferay, Inc.
> [Specification Name(s) and Version(s)]
> Portlet 2.0 Bridge for JavaServerâ„¢ Faces 1.2
> [Test Suite Name and Version]
> portlet-bridge-tck-main, v1.0.0
> [Exclude List Version]
> N/A
> [Test Name]
> TestPage203 (JSF_ELTest)
> [Complaint (argument for why test is invalid)]
> The JSF_ELTest verifies "facesContext" implicit object is equal to the value returned
by FacesContext.getCurrentInstance(). This works fine with Mojarra 1.2_03, but newer versions
of Mojarra have different behavior possibly due to
> In newer versions of Mojarra, the com.sun.faces.el.ImplicitObjectELResolver.getValue(ELContext
context, Object base, Object property) method returns an instance of com.sun.faces.context.FacesContextImpl,
which does not match the value returned by FacesContext.getCurrentInstance().
> I'm filing this as a TCK Challenge because Liferay Faces Bridge requires Mojarra 1.2_13-b01
(or newer) due to the following issue:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message