portals-pluto-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (PLUTO-444) Filter chain is not implemented the right way
Date Tue, 07 Apr 2009 01:48:12 GMT

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

Ate Douma resolved PLUTO-444.

    Resolution: Fixed

Patch was applied long time ago

> Filter chain is not implemented the right way
> ---------------------------------------------
>                 Key: PLUTO-444
>                 URL: https://issues.apache.org/jira/browse/PLUTO-444
>             Project: Pluto
>          Issue Type: Sub-task
>          Components: portal driver
>    Affects Versions: 1.1-286-COMPATIBILITY, 2.0.0
>            Reporter: Christian Raschka
>            Priority: Critical
>             Fix For: 1.1-286-COMPATIBILITY, 2.0.0
>         Attachments: filter.231107.patch, filters.271107.patch
> In my opinion portlet filter should work the same way like servlet filters do:
> An example: If you have a filter chain with filters F1 and F2, then the chain is: F1
-> F2 -> target -> F2 -> F1.
> An exception is, if a Filter does not call filterChain.doFilter. Then no other filter
_or_ the target is invoked and the filter itself is responsible for the response.
> (e.g. see http://java.sun.com/products/servlet/Filters.html)
> In the current implementation the target is invoked, no matter if a filter blocks the
chain or not.

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

View raw message