[
https://jira.jboss.org/browse/GTNPORTAL-1664?page=com.atlassian.jira.plug...
]
Chris Laprun commented on GTNPORTAL-1664:
-----------------------------------------
I don't have a definite way to reproduce the issue but I've seen it happen with
WSRP portlets when there's a problem with the remote producer. Note, though, that you
shouldn't need to reproduce the issue to fix it. It's just a matter of not
assuming the portletOfferedPortletContext is not null when producerOfferedPortlet is,
because as mentioned in my original description, when one is null, the other most likely
is as well. :)
NPE if portlet information cannot be retrieved
----------------------------------------------
Key: GTNPORTAL-1664
URL:
https://jira.jboss.org/browse/GTNPORTAL-1664
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.1.0-GA
Reporter: Chris Laprun
Labels: portal-s43, worked
Fix For: 3.2.0-GA
Original Estimate: 4 hours
Remaining Estimate: 4 hours
Caused by: java.lang.NullPointerException
at
org.exoplatform.portal.webui.application.UIPortlet.supportsPublicParam(UIPortlet.java:565)
at
org.exoplatform.portal.webui.application.UIPortlet.getPublicParameters(UIPortlet.java:683)
at org.exoplatform.portal.webui.application.UIPortlet.create(UIPortlet.java:714)
at
org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:186)
Basically, in the following code:
if (producedOfferedPortlet == null)
{
log.info("Could not find portlet with ID : " +
producerOfferedPortletContext.getId());
return null;
}
it's very likely that if producerOfferedPortlet is null, then the associated context
is as well... hence the NPE.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira