Portlet Bridge 3.0.0 -- renderURLs shouldn't carry forward scope by default
---------------------------------------------------------------------------
Key: PORTLETBRIDGE-182
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-182
Project: MyFaces Portlet Bridge
Issue Type: Bug
Components: Impl
Affects Versions: 3.0.0-alpha
Reporter: Michael Freedman
Assignee: Michael Freedman
Late in the game the bridge impl changed (2.0) whereby a bridge scope is always
created on any request that there isn't one (in the case you are in a render or
resource request we cache this in a session attr). Because of this renderURLs
created via encodeActionURL might retain their scopes across submissions. This
doesn't seem like the reasonable default. With Portlet 3.0.0 they added a
concept of a bookmarkable url -- which makes it more common for a faces app to
create a render url (prior versions could only do it using the special
portlet:render? syntax). So we need to fix the encodeActionURL to mark
renderURLs as not preserving the scope.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
