You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Eric Dalquist (JIRA)" <ji...@apache.org> on 2008/11/19 01:11:45 UTC
[jira] Resolved: (PLUTO-503) Expose createPortletScopedId and
isInCurrentPortletScope of PortletSessionImpl as protected
[ https://issues.apache.org/jira/browse/PLUTO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Dalquist resolved PLUTO-503.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0-refactoring)
Resolved for 1.1.7 in rev 718808
Resolved for 2.0.0 in rev 718811
> Expose createPortletScopedId and isInCurrentPortletScope of PortletSessionImpl as protected
> -------------------------------------------------------------------------------------------
>
> Key: PLUTO-503
> URL: https://issues.apache.org/jira/browse/PLUTO-503
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Reporter: Eric Dalquist
> Assignee: Eric Dalquist
> Fix For: 2.0.0, 1.1.7
>
> Attachments: portletSession.patch
>
>
> To allow the portal to define its own namespace and scoping rules the following methods and fields should be defined as protected
> String createPortletScopedId(String name)
> boolean isInCurrentPortletScope(String name)
> final InternalPortletWindow internalPortletWindow;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.