[JBoss JIRA] Created: (GTNPORTAL-1041) Add the possibility to overload default ressources bundle
by Romain Dénarié (JIRA)
Add the possibility to overload default ressources bundle
---------------------------------------------------------
Key: GTNPORTAL-1041
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1041
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0-GA
Reporter: Romain Dénarié
Hi,
I have a problem when I want to overload default resources bundle.
Do not change portal.war binary, I create exo-conf folder to externalise configuration. In this folder I define everything using specific resources bundle and it's working fine.
But when I want to overload existing bundle in portal.war, it is not working.
For example, if I want to add a node in portal classic navigation, I'm unable to internationalize the label. In fact, when RessourceBundleService loads ressources bundle files, it takes in priority the one in portal.war, which not contains my new node, even if ressources-bundle-configuration.xml is in exo-conf.
Same thing if I want to add a node in group /platform/administors navigation.
--
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
11 years, 11 months
[JBoss JIRA] Created: (GTNPORTAL-1131) Error should be more explicit when a portlet cannot be found
by Chris Laprun (JIRA)
Error should be more explicit when a portlet cannot be found
------------------------------------------------------------
Key: GTNPORTAL-1131
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1131
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: PC integration
Affects Versions: 3.0.0-GA
Reporter: Chris Laprun
Assignee: Matt Wringe
Priority: Minor
More specifically, it should be handled instead of throwing an NPE:
org.exoplatform.services.portletcontainer.PortletContainerException: java.lang.NullPointerException
at org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:308)
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)
...
Caused by: java.lang.NullPointerException
at org.exoplatform.portal.webui.application.UIPortlet.getPortletContext(UIPortlet.java:865)
at org.exoplatform.portal.webui.application.UIPortlet.create(UIPortlet.java:717)
at org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:186)
... 179 more
--
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
11 years, 11 months