[PB-47] FilterPortlet throws NPE on PortletConfig dependent methods when the managed portlet doesn't implement PortletConfig

• Type: Bug
• Status: Resolved
• Priority: Critical
• 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:46
• Updated: 02/May/13 02:28
• Resolved: 16/Sep/06 19:55

Description

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

<quote>
The portletConfig instance variable is used but never set. In the methods getInitParameter, getInitParameterNames, getPortletContext, getPortletName, & getResourceBundle you will get a NullPointerException if the Portlet being managed (portlet instance variable) is not an instance of PortletConfig.

Scott
</quote>

I checked the code and can confirm this bug.
As I already will provide a fix for PB-46, extending FilterPortlet from GenericPortlet, this will be easy to fix as GenericPortlet stores the PortletConfig itself.
So I will fix this issue together with PB-46.

Issue Links

• depends upon: PB-46 FilterPortlet cannot be used with ServletContextProvider because it doesn't extend GenericPortlet