[
https://issues.apache.org/jira/browse/PLUTO-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliot Metsger closed PLUTO-384.
--------------------------------
Resolution: Fixed
A PortletContainerException is now thrown when a application id (context)
cannot be found.
> PortletContextManager.getPortletApplicationDescriptor returns null when a
> portlet context cannot be found.
> ----------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-384
> URL: https://issues.apache.org/jira/browse/PLUTO-384
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 1.2.0, 1.1.3
> Reporter: Elliot Metsger
> Assignee: Elliot Metsger
> Priority: Minor
> Fix For: 1.2.0, 1.1.4
>
>
> PortletContextManager (which is the implementation of PortletRegistryService)
> returns null when a portlet context cannot be found:
> public PortletAppDD getPortletApplicationDescriptor(String applicationId)
> throws PortletContainerException {
> InternalPortletContext ipc = (InternalPortletContext)
> portletContexts.get(applicationId);
> if (ipc != null) {
> return ipc.getPortletApplicationDefinition();
> }
> LOG.warn("Unable to retrieve portlet application descriptor:
> '"+applicationId+"'");
> return null;
> }
> According to the PortletRegistryService interface, a
> PortletContainerException should be thrown if the descriptor can not be
> found or if the portlet.xml can not be parsed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
