You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michael Freedman (JIRA)" <de...@myfaces.apache.org> on 2010/01/19 22:43:54 UTC
[jira] Created: (PORTLETBRIDGE-108) Bridge FacesContext should set
currentInstance FacesContext on the ELContext
Bridge FacesContext should set currentInstance FacesContext on the ELContext
----------------------------------------------------------------------------
Key: PORTLETBRIDGE-108
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-108
Project: MyFaces Portlet Bridge
Issue Type: Bug
Components: Impl
Affects Versions: 2.0.0-alpha, 1.0.0-beta
Reporter: Michael Freedman
Assignee: Michael Freedman
Currently the bridge sets its FacesContext instance on the ELContext (so it can be grabbed later in resolvers)/and or used to verify we are running in a FacesContext . If someone has wrapped our context then there is a mismatch between the FacesContext.getCurrentInstance and the one we have set on the ELContext. Not only does this cause a TCK test to fail but is generally bad as the wrapee wouldn't be called/used in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PORTLETBRIDGE-108) Bridge FacesContext should set
currentInstance FacesContext on the ELContext
Posted by "Michael Freedman (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Freedman resolved PORTLETBRIDGE-108.
--------------------------------------------
Resolution: Fixed
Changed to set the CurrentInstance not use "this".
> Bridge FacesContext should set currentInstance FacesContext on the ELContext
> ----------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-108
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-108
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 1.0.0-beta, 2.0.0-alpha
> Reporter: Michael Freedman
> Assignee: Michael Freedman
>
> Currently the bridge sets its FacesContext instance on the ELContext (so it can be grabbed later in resolvers)/and or used to verify we are running in a FacesContext . If someone has wrapped our context then there is a mismatch between the FacesContext.getCurrentInstance and the one we have set on the ELContext. Not only does this cause a TCK test to fail but is generally bad as the wrapee wouldn't be called/used in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.