You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bridges-dev@portals.apache.org by "Ate Douma (JIRA)" <br...@portals.apache.org> on 2006/09/16 14:47:22 UTC
[jira] Created: (PB-47) FilterPortlet throws NPE on PortletConfig
dependent methods when the managed portlet doesn't implement PortletConfig
FilterPortlet throws NPE on PortletConfig dependent methods when the managed portlet doesn't implement PortletConfig
--------------------------------------------------------------------------------------------------------------------
Key: PB-47
URL: http://issues.apache.org/jira/browse/PB-47
Project: Portals Bridges
Issue Type: Bug
Components: filterportlet
Affects Versions: 1.0
Reporter: Ate Douma
Assigned To: Ate Douma
Priority: Critical
Fix For: 1.0.1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org
[jira] Work started: (PB-47) FilterPortlet throws NPE on
PortletConfig dependent methods when the managed portlet doesn't implement
PortletConfig
Posted by "Ate Douma (JIRA)" <br...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/PB-47?page=all ]
Work on PB-47 started by Ate Douma.
> FilterPortlet throws NPE on PortletConfig dependent methods when the managed portlet doesn't implement PortletConfig
> --------------------------------------------------------------------------------------------------------------------
>
> Key: PB-47
> URL: http://issues.apache.org/jira/browse/PB-47
> Project: Portals Bridges
> Issue Type: Bug
> Components: filterportlet
> Affects Versions: 1.0
> Reporter: Ate Douma
> Assigned To: Ate Douma
> Priority: Critical
> Fix For: 1.0.1
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org
[jira] Commented: (PB-47) FilterPortlet throws NPE on PortletConfig
dependent methods when the managed portlet doesn't implement PortletConfig
Posted by "Ate Douma (JIRA)" <br...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/PB-47?page=comments#action_12435221 ]
Ate Douma commented on PB-47:
-----------------------------
I've committed fixes for both PB-46 and this one: please review and comment
> FilterPortlet throws NPE on PortletConfig dependent methods when the managed portlet doesn't implement PortletConfig
> --------------------------------------------------------------------------------------------------------------------
>
> Key: PB-47
> URL: http://issues.apache.org/jira/browse/PB-47
> Project: Portals Bridges
> Issue Type: Bug
> Components: filterportlet
> Affects Versions: 1.0
> Reporter: Ate Douma
> Assigned To: Ate Douma
> Priority: Critical
> Fix For: 1.0.1
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org
[jira] Resolved: (PB-47) FilterPortlet throws NPE on PortletConfig
dependent methods when the managed portlet doesn't implement PortletConfig
Posted by "Ate Douma (JIRA)" <br...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/PB-47?page=all ]
Ate Douma resolved PB-47.
-------------------------
Resolution: Fixed
As reported by Scott the fixes solved his issues.
> FilterPortlet throws NPE on PortletConfig dependent methods when the managed portlet doesn't implement PortletConfig
> --------------------------------------------------------------------------------------------------------------------
>
> Key: PB-47
> URL: http://issues.apache.org/jira/browse/PB-47
> Project: Portals Bridges
> Issue Type: Bug
> Components: portletfilter
> Affects Versions: 1.0
> Reporter: Ate Douma
> Assigned To: Ate Douma
> Priority: Critical
> Fix For: 1.0.1
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org