[
https://issues.apache.org/jira/browse/PLUTO-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian DeHamer updated PLUTO-499:
--------------------------------
Attachment: FilterConfigImpl.java
Attached is an updated copy of FilterConfigImpl which includes a null check in
the getInitParameters method. This appears to solve the problem
> Invoking FilterConfig.getInitParameter() when there are no filter parameters
> defined results in NPE
> ---------------------------------------------------------------------------------------------------
>
> Key: PLUTO-499
> URL: https://issues.apache.org/jira/browse/PLUTO-499
> Project: Pluto
> Issue Type: Bug
> Components: portlet container
> Affects Versions: 2.0.0
> Environment: JDK 1.5.0_16, Tomcat 5.5.27
> Reporter: Brian DeHamer
> Fix For: 2.0.0
>
> Attachments: FilterConfigImpl.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
