myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott O'Bryan (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (TRINIDAD-1376) NullPointerException because RequestContext released after action request.
Date Mon, 26 Jan 2009 17:39:59 GMT

    [ https://issues.apache.org/jira/browse/TRINIDAD-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667318#action_12667318
] 

Scott O'Bryan commented on TRINIDAD-1376:
-----------------------------------------

The RequestContext should be released and re-created each request.  By spec, request scoped
attributes DO NOT have to carry over from an Action to a Render.  The global configurator
will run again in the action phase and restore this object.  Currently this logic works fine
with the JSR-301 Portlet Bridge.  Can you provide an example which illustrates your issue?

> NullPointerException because RequestContext released after action request.
> --------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1376
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1376
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Portlet
>    Affects Versions:  1.2.11-core
>            Reporter: Felix Röthenbacher
>
> RequestContext is released after action request which results in a NullPointerException
in the following render request.
> The problem is in the method GlobalConfiguratorImpl.endRequest(final ExternalContext
externalContext)
> Calling _releaseRequestContext(externalContext); removes the RequestContext from ThreadLocal.
> Any subsequent calls to RequestContext.getCurrentInstance() return null which breaks
the render request.

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


Mime
View raw message