[PB-46] FilterPortlet cannot be used with ServletContextProvider because it doesn't extend GenericPortlet

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.0.1
• Component/s: portletfilter
• Assignee: Ate Douma
• Reporter: Ate Douma
• Created: 16/Sep/06 12:39
• Updated: 02/May/13 02:28
• Resolved: 16/Sep/06 19:55

Description

Scott Anderson reported the following on the bridges-user mailing list:

<quote>
I was hoping to use the ServletContextProvider interface for obtaining the ServletContext, ServletRequest, & ServletResponse given a FilterPortlet implementation. Unfortunately, the ServletContextProvider requires that it be provided a GenericPortlet which FilterPortlet is not. I am going to go ahead and roll my own FilterPortlet that is a subclass of GenericPortlet but I thought I'd note this inconsistency so that this problem can hopefully be resolved in a subsequent release of Portals Bridges.

Scott
</quote>

After checking the current implementation of FilterPortlet which only implements the Portlet and PortletConfig interfaces (just as GenericPortlet), I think simply extending GenericPortlet will do the trick and should have no unexpected side-effects.

Issue Links

• is depended upon by: PB-47 FilterPortlet throws NPE on PortletConfig dependent methods when the managed portlet doesn't implement PortletConfig