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/06/23 18:28:45 UTC
[jira] Updated: (PLUTO-489) Refactor request attribute handling
into optional service interface
[ https://issues.apache.org/jira/browse/PLUTO-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Dalquist updated PLUTO-489:
--------------------------------
Attachment: pluto_reqAttr.patch
This patch refactors the existing request attribute handling, including generation of the USER_INFO Map into an optional service. This patch is functionally identical and the only catch that upgrades may run into is if they implement OptionalContainerServices directly there is a new method RequestAttributeService getRequestAttributeService(); on the interface. Implementing the method is very easy and non-intrusive for portals using Pluto.
> Refactor request attribute handling into optional service interface
> -------------------------------------------------------------------
>
> Key: PLUTO-489
> URL: https://issues.apache.org/jira/browse/PLUTO-489
> Project: Pluto
> Issue Type: Improvement
> Reporter: Eric Dalquist
> Assignee: Eric Dalquist
> Fix For: 2.0.0, 1.1.6
>
> Attachments: pluto_reqAttr.patch
>
>
> To allow portal more control over request attribute processing and generation without having to re-implement the entire PortletRequest object model the request attribute handling methods in PortletRequest should delegate to an optional service interface.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.