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/08 12:19:29 UTC

[jira] Updated: (PLUTO-371) Portlet Filter

     [ https://issues.apache.org/jira/browse/PLUTO-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Torsten Dettborn updated PLUTO-371:
-----------------------------------

        Fix Version/s: 1.1-286-trunk-merge
    Affects Version/s: 1.1-286-trunk-merge

> Portlet Filter
> --------------
>
>                 Key: PLUTO-371
>                 URL: https://issues.apache.org/jira/browse/PLUTO-371
>             Project: Pluto
>          Issue Type: New Feature
>    Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>            Reporter: Torsten Dettborn
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: Filter_API_r15_050607.patch, mylar-context.zip
>
>
> Portlet filters are components to transform the request or response from a portlet. You have filter lifecycle for action-, event-,render- and resourceRequest/Response. The configurations is defined in the deployment descriptor. There is only one filter instance for each filter in the portlet application. For more details see the Portlet Specification Version 2.0 early draft 2 rev. 14.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.