You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "David DeWolf (JIRA)" <pl...@jakarta.apache.org> on 2005/07/23 06:36:02 UTC

[jira] Resolved: (PLUTO-130) PortletApplicationEntity.getPortletApplicationDefinition() causes NPE when the portletentityregistry.xml references a portlet that doesn't exist.

     [ http://issues.apache.org/jira/browse/PLUTO-130?page=all ]
     
David DeWolf resolved PLUTO-130:
--------------------------------

    Fix Version: 1.0.1-rc4
     Resolution: Fixed

Modified/Peices of patch applied.  More specific messages are in place.  Thank you Elliot. Completed: At revision: 224441  


> PortletApplicationEntity.getPortletApplicationDefinition() causes NPE when the portletentityregistry.xml references a portlet that doesn't exist.
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: PLUTO-130
>          URL: http://issues.apache.org/jira/browse/PLUTO-130
>      Project: Pluto
>         Type: Improvement
>   Components: portal driver
>     Versions: 1.0.1-rc3
>  Environment: Sun JDK 1.4.2
>     Reporter: Elliot Metsger
>     Assignee: David DeWolf
>     Priority: Minor
>      Fix For: 1.0.1-rc4

>
> For example if the portletentityregistry.xml defines an entity that doesn't exist, currently an NPE is thrown in o.a.p.portalImpl.om.entity.impl.PortletEntityImpl's getPortletDefinition() method (because the PortletApplicationEntity cannot load the corresponding - non-existant - PortletApplicatonDefinition).
> Can we throw an explicit NPE containing an error message?

-- 
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