[gatein-issues] [JBoss JIRA] Commented: (GTNPC-19) No portlet info section in portlet.xml leads to display a portlet error
[
https://jira.jboss.org/jira/browse/GTNPC-19?page=com.atlassian.jira.plugi...
]
Matt Wringe commented on GTNPC-19:
----------------------------------
for the portlet 2.0 xsd, that xml fragment is valid.
<sequence>
..
<element name="resource-bundle" type="portlet:resource-bundleType"
minOccurs="0"/>
<element name="portlet-info" type="portlet:portlet-infoType"
minOccurs="0"/>
..
</sequence>
For the portlet 1.0 case, then yes your argument seems valid. I don't think we should
be adding the portlet-title if the portlet-section exists but doesn't specify the
title. The current implementation does this, and it is probably the incorrect behaviour.
It should be up to the portlet developer to configure the portlet title. Although I
don't want think we want to change this behaviour as it could break backwards
compatibility with current portlets.
We can't throw the error at deploy time, it has to be done at runtime. The portlet
itself can specify the title, the deployment descriptors are valid if no resource-bundle
or portlet-title section is specified.
No portlet info section in portlet.xml leads to display a portlet
error
-----------------------------------------------------------------------
Key: GTNPC-19
URL: https://jira.jboss.org/jira/browse/GTNPC-19
Project: GateIn Portlet Container
Issue Type: Bug
Reporter: Julien Viet
Assignee: Matt Wringe
Attachments: pc-empty-portlet-info.patch
java.util.MissingResourceException: Can't find resource for bundle
org.gatein.common.i18n.ParentChildResourceBundle, key javax.portlet.title
at java.util.ResourceBundle.getObject(ResourceBundle.java:325)
at java.util.ResourceBundle.getString(ResourceBundle.java:285)
at javax.portlet.GenericPortlet.getTitle(GenericPortlet.java:261)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:232)
at
org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl$Invoker.doFilter(PortletContainerImpl.java:569)
at
org.gatein.pc.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:159)
at
org.gatein.pc.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:80)
at
org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:506)
at
org.gatein.pc.portlet.container.ContainerPortletDispatcher.invoke(ContainerPortletDispatcher.java:42)
followed by
java.lang.NullPointerException
at
org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:293)
at
org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:61)
at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:148)
at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:368)
at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:358)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira