[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013640#comment-13013640
]
Michael Freedman commented on PORTLETBRIDGE-202:
------------------------------------------------
PortletExternalContextImpl.encodeFacesActionTarget does the encoding of the
target (admittedly now that you have pointed it out it would be better if it
also checked response.getPortletMode()). This is called when encodeActionURL
is called with an URL that resolves to a Faces view.
doFacesRequest (renderRequest/whatever) in BridgeImpl calls hasModeChanged() to
detect whether the mode of the request is different than the one of the target
viewId.
> Proposal for 3.0 IMPL: Support mode changes via
> StateAwareResponse#setPortletMode(PortletMode)
> ----------------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-202
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-202
> Project: MyFaces Portlet Bridge
> Issue Type: New Feature
> Components: General
> Affects Versions: 3.0.0
> Reporter: Neil Griffin
> Assignee: Michael Freedman
>
> To the best of my knowledge, the Bridge 2.0 spec does not address usage of
> StateAwareResponse#setPortletMode(PortletMode) within a JSF backing bean
> action.
> This proposal would require the BridgeRequestScope to remember the
> PortletMode so that mode changes can be detected:
> public interface BridgeRequestScope {
> ...
> PortletMode getPortletMode();
> void setPortletMode(PortletMode portletMode);
> ...
> }
> Note that the Bridge implementation would be required to call
> bridgeRequestScope.setPortletMode() during an ActionRequest and EventRequest.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
