[
https://issues.apache.org/jira/browse/PLUTO-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552475
]
Craig Doremus commented on PLUTO-371:
-------------------------------------
I'm not sure what part of PLUTO-233 that is missing in the trunk-merge branch?
I checked out the TCKDriverServlet and it appears to be the same as the trunk
(except lines 115-116 that were recently commented out by Torsten). Please
advise?
I'm also unsure what patch in this issue that you want me to apply. I looked at
the Filter_API_r15_050607.patch and saw that it was from rev 15 of the Portlet
2.0 API. I don't want to overwrite things that have changed sunsequently (since
we are now at rev 30). Can you (or anyone else) point me to what's in the patch
that's missing from the 1.1-286-trunk-merge branch?
Thank you.
> 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,
> PortletFilter_090807.patch
>
>
> 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.
