[PLUTO-499] Invoking FilterConfig.getInitParameter() when there are no filter parameters defined results in NPE

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-refactoring, 2.0.0
• Fix Version/s: 2.0-refactoring, 2.0.0
• Component/s: portlet container
• Environment: JDK 1.5.0_16, Tomcat 5.5.27
• Assignee: Unassigned
• Reporter: Brian DeHamer
• Created: 11/Sep/08 19:39
• Updated: 04/Oct/08 03:59
• Resolved: 04/Oct/08 03:59

Description

Within the init() method of a PortletFilter, if you invoke the GetInitParameter() method of the passed-in FilterConfig object a NullPointerException is thrown if the filter has been configured with NO initialization parameters. The NPE comes from

org.apache.pluto.driver.services.container.FilterConfigImpl.getInitParameter(FilterConfigImpl.java:48)

If you configure the portlet filter with ANY initiailization parameters the NPE is avoided.

According to the JSR286 spec it seems that any call to GetInitParameter() that references a non-existent initialization parameter should return null.