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/02/19 23:36:28 UTC

[jira] Resolved: (PORTLETBRIDGE-122) BridgeUtil.isPortletRequest throws nullPointerException is no tin FacesContext

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

Michael Freedman resolved PORTLETBRIDGE-122.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.0.0

Now checks to make sure that the FacesContext is non-null before deref.

> BridgeUtil.isPortletRequest throws nullPointerException is no tin FacesContext
> ------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-122
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-122
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.0.0-beta, 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 1.0.0, 2.0.0
>
>
> This method wil throw a NullPointerException if there is no current FacesContext.  As the bridge adds a Application impl that overrides createComponent which calls on this method -- its possible that createComponent is called during Faces configuration/initialization (via a ServletContextListener) and there is no FacesContext.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.