[
https://issues.apache.org/jira/browse/TRINIDAD-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633793#action_12633793
]
Scott O'Bryan commented on TRINIDAD-1239:
-----------------------------------------
This patch violated the contract of configurators. There is still some work to
be done for 301 and I'm slated to do that soon, but the configurators have a
lifespan of a "physical" request. Only the global configurator is to be run
during each "phase" of the bridge. Allowing the beginRequest and endRequest
methods to be executed durring the action AND render phases is something that
I'm adding in the standalone configurators via an annotation but does NOT yet
exist in Trinidad.
Items in the Bridge's managed request scope will be automatically preserved by
the bridge. Currently for Trinidad, this is most of the objects. There are a
few objects which are supposed to span a single action/render. Right now that
logic is broken, but changing the contract is not what is needed to fix this.
I'm going to keep this bug open, but the answer will likely be to add an API to
configurator to save state information. This would, essentially, copy the
state information to the session at the end of the ActionRequest, and then
restore it at the beginning of the subsequent render request based on a
RenderParameter for the key. Unlike the managed request scope in JSR-301, this
would go away after a single action/render request pair.
> Error when using with MyFaces portlet bridge JSR-301
> ----------------------------------------------------
>
> Key: TRINIDAD-1239
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1239
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Portlet
> Affects Versions: 1.2.10-core
> Environment: IBM WebSphere Portal 6.1
> Reporter: Felix Röthenbacher
> Attachments: GlobalConfiguratorImpl.java.diff
>
>
> The JSR-301 specification handles the action request and the render
> request(s) as independent requests. Trinidad tries to keep some information
> between the two requests if running in portlet mode. This prevents it from
> running with MyFaces portlet bridge in a Websphere Portal environment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
