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/03/18 22:42:27 UTC

[jira] Deleted: (PORTLETBRIDGE-128) BridgeUtil needs to account for not running in a Faces context

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

Michael Freedman deleted PORTLETBRIDGE-128:
-------------------------------------------


> BridgeUtil needs to account for not running in a Faces context
> --------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-128
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-128
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>
> The static utility methods in BridgeUtil (like isPortletRequest()) rely on getting at the request attributes via the ExternalContext (reqquestMap).  You get a nullPointerException if this is called prior to a FacesContext being established.  This can occur when the bridge's Application impl is being activated by the Faces configurator at startup.  Code should instead check for a null FacesContext and merely return a value indicating we aren't in a portlet request.

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