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 "Torsten Dettborn (JIRA)" <ji...@apache.org> on 2007/09/11 22:50:32 UTC
[jira] Updated: (PLUTO-431) PortletUrl listener
[ https://issues.apache.org/jira/browse/PLUTO-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Torsten Dettborn updated PLUTO-431:
-----------------------------------
Attachment: PortletURLGenerationListener091107.patch
The patch implements the Portlet URL listener. It is called in the BaseURLImpl and with the register in the deployment descriptor all filters will call in the right order.
> PortletUrl listener
> -------------------
>
> Key: PLUTO-431
> URL: https://issues.apache.org/jira/browse/PLUTO-431
> Project: Pluto
> Issue Type: New Feature
> Components: portal driver, portlet container
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Torsten Dettborn
> Assignee: Torsten Dettborn
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: PortletURLGenerationListener091107.patch
>
>
> Here is a short abstract what the PortletUrl listener should do:
> Portlets can register portlet URL listeners in order to filter URLs before they get
> generated either as string the toString or written to the output stream via the write
> method of the BaseURL interface. For example the portlet could use such a listener to set
> the caching level of resource URLs in one central piece of code.
> In order to receive a callback from the portlet container before a portlet URL is generated
> the portlet needs to implement the PortletURLGenerationListener interface and
> register it in the deployment descriptor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.