[
https://issues.apache.org/jira/browse/TRINIDAD-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668994#action_12668994
]
Scott O'Bryan commented on TRINIDAD-1376:
-----------------------------------------
Actually this issue is a little more complex if we take remote WSRP Portals
into account. The Configurators were written to an earlier version of the
bridge spec and I made the assumption that request scoped attributes would
continue for a full lifecycle request. The EG is still considering this
proposal from me, but right now this is not the case.
What I basically need to do is create a state-map which uses the session to
jump from action-request to render request. I have a prototype of this in my
portlet branch and I'll backport a cleaner version to the Trinidad trunk
hopefully today.
> 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
> Assignee: Scott O'Bryan
> Attachments: TRINIDAD-1376-patch.txt
>
>
> 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.
