[
https://issues.apache.org/jira/browse/PLUTO-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552331
]
Christian Raschka commented on PLUTO-444:
-----------------------------------------
It seems, that there is a problem, with the moment the filter configs are
loaded. Craig could you please test, if everything is ok, if you restart tomcat
after deploying the portlet.
With me the filterchain isn't found after deploying, and therefor rendering
doesn't occur (it is the last entry in the FilterChain.)
Btw. the comment should be: "Should be called in the FilterChain" and it is in
the patch.
> 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, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Priority: Critical
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> 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.
