[
https://issues.apache.org/jira/browse/PLUTO-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552555
]
cdoremus edited comment on PLUTO-371 at 12/17/07 2:36 PM:
---------------------------------------------------------------
Thanks for the tip, Christian. I refactored SupportedModesServiceImpl in
1.1-286-trunk-merge branch to put back the loadPortletModes() method from the
1.1-286-COMPATBILITY branch in SVN rev 605023. I also got rid of a couple of
unused methods.
Having FIlterManagerImpl initialization code in this class is poor
encapsulation and should be refactored into another class that
DriverConfiguration loads at startup.
was (Author: cdoremus):
Thanks for the tip, Christian. I refactored SupportedModesServiceImpl in
1.1-286-trunk-merge branch to put back the loadPortletModes() method from the
1.1-286-COMPATBILITY branch. I also got rid of a couple of unused methods.
Having FIlterManagerImpl initialization code in this class is poor
encapsulation and should be refactored into another class that
DriverConfiguration loads at startup.
> 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.
