[JBoss JIRA] (GTNPORTAL-2406) Fully scope the Portlet Container Engine to the RootContainer
by Nicolas Filotto (JIRA)
Nicolas Filotto created GTNPORTAL-2406:
------------------------------------------
Summary: Fully scope the Portlet Container Engine to the RootContainer
Key: GTNPORTAL-2406
URL: https://issues.jboss.org/browse/GTNPORTAL-2406
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: PC integration
Affects Versions: 3.2.0-GA
Reporter: Nicolas Filotto
Assignee: Matt Wringe
The current integration of the PC is incorrect as we have one half scoped to the RootContainer (the FederatingPortletInvoker) and the rest to the PortalContainers. The goal of this task is to see if the integration can be reviewed to scope everything to the RootContainer, this way we will also have only one PC engine for all the portal containers.
See below one way to do it:
# Remove any references of the TopContainer and the ResourceBundleService from ExoKernelIntegration
# Remove the configuration file portal/WEB-INF/conf/common/portlet-container-configuration.xml (or at least its content)
# Configure the component ExoKernelIntegration in conf/configuration.xml that will be internal to exo.portal.component.pc
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-910) No portlet info section in portlet.xml leads to display a portlet error
by Julien Viet (JIRA)
No portlet info section in portlet.xml leads to display a portlet error
-----------------------------------------------------------------------
Key: GTNPORTAL-910
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-910
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0-GA
Reporter: Julien Viet
Assignee: Matt Wringe
Fix For: 3.1.0-GA
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
12 years, 1 month
[JBoss JIRA] (GTNPORTAL-2400) Default redirect configuration for the portal
by Matt Wringe (JIRA)
Matt Wringe created GTNPORTAL-2400:
--------------------------------------
Summary: Default redirect configuration for the portal
Key: GTNPORTAL-2400
URL: https://issues.jboss.org/browse/GTNPORTAL-2400
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Mobile
Reporter: Matt Wringe
Assignee: Matt Wringe
Research and test a good default configuration to the redirection to a mobile site.
There should be two example configurations:
1) redirect to a mobile site, where mobile in this case means a touch enabled phone or tablet. This should be easier to handle (check for specific keywords in the UA or use a test if the browser is touch enabled or not)
2) redirect to a phone specific site or to a tablet specific site. A bit more complex, if using device width or height, then we need to take into affect the pixel density (ie a high pixel density screen could have a large width/height but a small screen size). Probably need to do some logic in the device detection page based on device diagonal (to get around width/height switching if device is physically rotated) and the pixel density.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month