[JBoss JIRA] (GTNPORTAL-3250) The portlets cannot be displayed after a portal reload
by Nicolas Filotto (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3250?page=com.atlassian.jira.pl... ]
Nicolas Filotto commented on GTNPORTAL-3250:
--------------------------------------------
# For me you should not take into account the warnings that actually occur while stopping the portal container.
# The error that you get, is something coming from wsrp as you can see in the stack trace {{Caused by: java.lang.IllegalStateException: A Plugins implementation (org.gatein.integration.wsrp.plugins.AS7Plugins) has already been provided}}, for me the code of wsrp should be reviewed to support hot reloading.
> The portlets cannot be displayed after a portal reload
> ------------------------------------------------------
>
> Key: GTNPORTAL-3250
> URL: https://issues.jboss.org/browse/GTNPORTAL-3250
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: PC integration
> Affects Versions: 3.6.1.Final
> Reporter: Nicolas Filotto
> Assignee: Marko Strukelj
> Attachments: GTNPORTAL-3250.patch
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> If you launch Gatein in developing mode, it is possible to reload only a given portal container either automatically by redeploying a webapp that has been defined as a PortalContainerConfigOwner (in other words you have the listener org.exoplatform.container.web.PortalContainerConfigOwner in your web.xml) or manually using the JMX console. And when you do so, no portlet can be displayed properly anymore (we have the message "This portlet encountered an error and could not be displayed" for all portlets), this issue is due to https://issues.jboss.org/browse/GTNPORTAL-2406.
> Here are the steps to reproduce:
> * Start GateIn with ./standalone.sh -Dexo.product.developing=true
> * launch the JMX Console and call _reload_ with the argument _portal_ on the MBean {{exo:container=root}}
> * Once the command is over, go to http://localhost:8080/portal/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-3250) The portlets cannot be displayed after a portal reload
by Thomas Heute (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3250?page=com.atlassian.jira.pl... ]
Thomas Heute commented on GTNPORTAL-3250:
-----------------------------------------
Just throwing a random idea.
Does it require: https://github.com/exoplatform/kernel/pull/27 to be included ?
(Again haven't looked at the code, I just know that the 2 were worked together)
> The portlets cannot be displayed after a portal reload
> ------------------------------------------------------
>
> Key: GTNPORTAL-3250
> URL: https://issues.jboss.org/browse/GTNPORTAL-3250
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: PC integration
> Affects Versions: 3.6.1.Final
> Reporter: Nicolas Filotto
> Assignee: Marko Strukelj
> Attachments: GTNPORTAL-3250.patch
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> If you launch Gatein in developing mode, it is possible to reload only a given portal container either automatically by redeploying a webapp that has been defined as a PortalContainerConfigOwner (in other words you have the listener org.exoplatform.container.web.PortalContainerConfigOwner in your web.xml) or manually using the JMX console. And when you do so, no portlet can be displayed properly anymore (we have the message "This portlet encountered an error and could not be displayed" for all portlets), this issue is due to https://issues.jboss.org/browse/GTNPORTAL-2406.
> Here are the steps to reproduce:
> * Start GateIn with ./standalone.sh -Dexo.product.developing=true
> * launch the JMX Console and call _reload_ with the argument _portal_ on the MBean {{exo:container=root}}
> * Once the command is over, go to http://localhost:8080/portal/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-2751) <priority> in navigation.xml files ignored for merge importMode
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2751?page=com.atlassian.jira.pl... ]
Trong Tran commented on GTNPORTAL-2751:
---------------------------------------
Actually the navigation importer still works properly, even with merge importMode.
The root problem here is at initializing time, the creating group/user event listeners (GroupPortalConfigListener and UserPortalConfigListener) from Organization Service triggers to load and import the default pre-defined site config at last (after data initializing process). That's why we couldn't overwrite the group/user site config properly from extension
> <priority> in navigation.xml files ignored for merge importMode
> ----------------------------------------------------------------
>
> Key: GTNPORTAL-2751
> URL: https://issues.jboss.org/browse/GTNPORTAL-2751
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Trong Tran
> Original Estimate: 4 hours
> Time Spent: 1 day, 2 hours
> Remaining Estimate: 1 hour
>
> Steps to reproduce:
> Clone the Portal Extension Quickstart and deploy it changing the {{<priority>}} value in {{war/src/main/webapp/WEB-INF/conf/sample-ext/portal/group/platform/administrators/navigation.xml}}.
> NOT OK: The changes have no effect, because priority is ignored in {{org.exoplatform.portal.mop.importer.NavigationImporter.perform()}} with {{importMode}} {{merge}}.
> h3. Solution Proposal A
> * Make {{<priority>}} optional in {{gatein_objects}} XSD and {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}}
> * Explicitly state in the documentation [1] that {{<priority>}} is considered only if not already set (first wins).
> h3. Solution Proposal B
> * Make {{<priority>}} optional in {{gatein_objects}} XSD and {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}}
> * Change the behavior of {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}} to the effect that {{<priority>}} is handled in the same way as navigation nodes: it is used or ignored according to the chosen {{importMode}}. Esp. for {{importMode}} {{merge}} the last read {{<priority>}} should win.
> * Document it in [1]
> For both A and B the most or all occutences of {{<priority>}} should be removed from Portal Extension Quickstart.
> [1] [https://docs.jboss.org/author/display/GTNPORTAL35/Portal+Navigation+Confi...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-3250) The portlets cannot be displayed after a portal reload
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3250?page=com.atlassian.jira.pl... ]
Peter Palaga commented on GTNPORTAL-3250:
-----------------------------------------
The fix does not seem to work as expected. I tested both GTNPORTAL-2394 and GTNPORTAL-3250 with these sources: https://github.com/ppalaga/gatein-portal/tree/GTNPORTAL-3250-2394
performing {{reload(portal)}} over jconsole results in a couple of warnings and then an error:
{code}
20:56:32,481 INFO [exo.kernel.container.RootContainer] (RMI TCP Connection(4)-127.0.0.1) Trying to reload the portal container 'portal'
20:56:32,482 INFO [exo.kernel.container.RootContainer] (RMI TCP Connection(4)-127.0.0.1) Trying to stop the portal container 'portal'
20:56:32,524 INFO [exo.jcr.component.core.SearchIndex] (RMI TCP Connection(4)-127.0.0.1) Index closed: /home/ppalaga/scratch/gatein-portal-master/wildFly/standalone/data/gatein/jcr/lucene/portal-system_portal
20:56:32,529 INFO [exo.jcr.component.core.SearchIndex] (RMI TCP Connection(4)-127.0.0.1) Index closed: /home/ppalaga/scratch/gatein-portal-master/wildFly/standalone/data/gatein/jcr/lucene/portal-work_portal
20:56:32,536 INFO [exo.jcr.component.core.SearchIndex] (RMI TCP Connection(4)-127.0.0.1) Index closed: /home/ppalaga/scratch/gatein-portal-master/wildFly/standalone/data/gatein/jcr/lucene/wsrp-system_portal
20:56:32,543 INFO [exo.jcr.component.core.SearchIndex] (RMI TCP Connection(4)-127.0.0.1) Index closed: /home/ppalaga/scratch/gatein-portal-master/wildFly/standalone/data/gatein/jcr/lucene/pc-system_portal
20:56:32,545 INFO [exo.jcr.component.core.SearchIndex] (RMI TCP Connection(4)-127.0.0.1) Index closed: /home/ppalaga/scratch/gatein-portal-master/wildFly/standalone/data/gatein/jcr/lucene/system_portal_system
20:56:32,548 INFO [exo.jcr.component.core.SearchIndex] (RMI TCP Connection(4)-127.0.0.1) Index closed: /home/ppalaga/scratch/gatein-portal-master/wildFly/standalone/data/gatein/jcr/lucene/system_portal
20:56:32,706 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,707 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,709 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,709 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,710 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,711 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,712 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,712 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,713 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,714 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,715 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,717 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,718 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,719 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,720 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,721 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,722 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,722 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,723 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,724 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,725 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,725 WARN [org.exoplatform.portal.resource.MainResourceResolver] (RMI TCP Connection(4)-127.0.0.1) Cannot find servlet context module
20:56:32,731 WARN [exo.jcr.component.core.RepositoryImpl] (RMI TCP Connection(4)-127.0.0.1) Repository repository is OFFLINE.
20:56:32,740 INFO [javax.portlet.faces] (RMI TCP Connection(4)-127.0.0.1) Destroy GenericFacesPortlet for portlet RedirectsAndImportExportAdminPortlet
20:56:32,742 INFO [javax.portlet.faces] (RMI TCP Connection(4)-127.0.0.1) Destroy GenericFacesPortlet for portlet WSRPConfigurationPortlet
20:56:32,758 INFO [exo.kernel.container.RootContainer] (RMI TCP Connection(4)-127.0.0.1) The portal container 'portal' has been stopped successfully
20:56:32,761 INFO [exo.kernel.container.RootContainer] (RMI TCP Connection(4)-127.0.0.1) Trying to restart the portal container 'portal'
20:56:32,762 INFO [exo.kernel.container.RootContainer] (RMI TCP Connection(4)-127.0.0.1) Trying to create the portal container 'portal'
20:56:33,464 INFO [org.exoplatform.web.security.codec.CodecInitializer] (RMI TCP Connection(4)-127.0.0.1) Initialized codec using builder org.exoplatform.web.security.codec.JCASymmetricCodecBuilder
20:56:33,489 INFO [exo.jcr.component.ext.NodeHierarchyCreatorImpl] (RMI TCP Connection(4)-127.0.0.1) The NodeHierarchyCreator is configured to use the new distribution mechanism for the users directories, if you prefer to use the old mechanism set the value parameter 'old-user-distribution' to 'true'.
20:56:33,501 ERROR [exo.kernel.container.RootContainer] (RMI TCP Connection(4)-127.0.0.1) Cannot create the portal container 'portal' . ServletContext: org.apache.catalina.core.ApplicationContextFacade@5be01333: java.lang.RuntimeException: Cannot instantiate component key=org.gatein.integration.wsrp.WSRPServiceIntegration type=org.gatein.integration.wsrp.WSRPServiceIntegration found at jndi:/default-host/gatein-wsrp-integration/WEB-INF/conf/wsrp/wsrp-configuration.xml
at org.exoplatform.container.jmx.MX4JComponentAdapter.getComponentInstance(MX4JComponentAdapter.java:131) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.management.ManageableComponentAdapter.getComponentInstance(ManageableComponentAdapter.java:58) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.ConcurrentContainer.getInstance(ConcurrentContainer.java:428) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.ConcurrentContainer.getComponentInstancesOfType(ConcurrentContainer.java:324) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.LifecycleVisitor.visitContainer(LifecycleVisitor.java:148) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.LifecycleVisitor.traverse(LifecycleVisitor.java:88) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.LifecycleVisitor.start(LifecycleVisitor.java:157) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.ConcurrentContainer.start(ConcurrentContainer.java:454) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.AbstractContainer.start(AbstractContainer.java:67) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.AbstractContainer.start(AbstractContainer.java:67) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.AbstractContainer.start(AbstractContainer.java:67) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.ExoContainer.start(ExoContainer.java:257) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.PortalContainer.start(PortalContainer.java:682) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.ExoContainer.start(ExoContainer.java:230) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.RootContainer.createPortalContainer(RootContainer.java:682) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.RootContainer.reload(RootContainer.java:1008) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:75) [rt.jar:1.7.0_25]
at sun.reflect.GeneratedMethodAccessor123.invoke(Unknown Source) [:1.7.0_25]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:279) [rt.jar:1.7.0_25]
at javax.management.modelmbean.RequiredModelMBean$4.run(RequiredModelMBean.java:1245) [rt.jar:1.7.0_25]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25]
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) [rt.jar:1.7.0_25]
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1239) [rt.jar:1.7.0_25]
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1077) [rt.jar:1.7.0_25]
at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:71) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_25]
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) [rt.jar:1.7.0_25]
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498)
at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1487) [rt.jar:1.7.0_25]
at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:97) [rt.jar:1.7.0_25]
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1328) [rt.jar:1.7.0_25]
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1420) [rt.jar:1.7.0_25]
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:848) [rt.jar:1.7.0_25]
at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) [:1.7.0_25]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322) [rt.jar:1.7.0_25]
at sun.rmi.transport.Transport$1.run(Transport.java:177) [rt.jar:1.7.0_25]
at sun.rmi.transport.Transport$1.run(Transport.java:174) [rt.jar:1.7.0_25]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25]
at sun.rmi.transport.Transport.serviceCall(Transport.java:173) [rt.jar:1.7.0_25]
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553) [rt.jar:1.7.0_25]
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808) [rt.jar:1.7.0_25]
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
Caused by: java.security.PrivilegedActionException: java.lang.reflect.InvocationTargetException
at org.exoplatform.commons.utils.SecurityHelper.doPrivilegedExceptionAction(SecurityHelper.java:318) [exo.kernel.commons-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.jmx.MX4JComponentAdapter.createInstance(MX4JComponentAdapter.java:148) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.jmx.MX4JComponentAdapter.getComponentInstance(MX4JComponentAdapter.java:120) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
... 53 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_25]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_25]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_25]
at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_25]
at org.exoplatform.container.ConcurrentContainer.createComponent(ConcurrentContainer.java:593) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.AbstractContainer.createComponent(AbstractContainer.java:213) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.AbstractContainer.createComponent(AbstractContainer.java:213) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.AbstractContainer.createComponent(AbstractContainer.java:213) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.container.jmx.MX4JComponentAdapter$1.run(MX4JComponentAdapter.java:156) [exo.kernel.container-2.5.0-Alpha1.jar:2.5.0-Alpha1]
at org.exoplatform.commons.utils.SecurityHelper.doPrivilegedExceptionAction(SecurityHelper.java:310) [exo.kernel.commons-2.5.0-Alpha1.jar:2.5.0-Alpha1]
... 55 more
Caused by: java.lang.IllegalStateException: A Plugins implementation (org.gatein.integration.wsrp.plugins.AS7Plugins) has already been provided
at org.gatein.wsrp.api.plugins.PluginsAccess.register(PluginsAccess.java:51) [wsrp-integration-api-2.2.11.Final.jar:2.2.11.Final]
at org.gatein.integration.wsrp.WSRPServiceIntegration.<init>(WSRPServiceIntegration.java:154) [extension-component-3.7.0.Alpha01-SNAPSHOT.jar:3.7.0.Alpha01-SNAPSHOT]
... 65 more
20:56:33,579 INFO [exo.kernel.container.RootContainer] (RMI TCP Connection(4)-127.0.0.1) The portal container 'portal' has been reloaded successfully in 1098 ms
{code}
Can it be that I am doing something wrong?
> The portlets cannot be displayed after a portal reload
> ------------------------------------------------------
>
> Key: GTNPORTAL-3250
> URL: https://issues.jboss.org/browse/GTNPORTAL-3250
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: PC integration
> Affects Versions: 3.6.1.Final
> Reporter: Nicolas Filotto
> Assignee: Marko Strukelj
> Attachments: GTNPORTAL-3250.patch
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> If you launch Gatein in developing mode, it is possible to reload only a given portal container either automatically by redeploying a webapp that has been defined as a PortalContainerConfigOwner (in other words you have the listener org.exoplatform.container.web.PortalContainerConfigOwner in your web.xml) or manually using the JMX console. And when you do so, no portlet can be displayed properly anymore (we have the message "This portlet encountered an error and could not be displayed" for all portlets), this issue is due to https://issues.jboss.org/browse/GTNPORTAL-2406.
> Here are the steps to reproduce:
> * Start GateIn with ./standalone.sh -Dexo.product.developing=true
> * launch the JMX Console and call _reload_ with the argument _portal_ on the MBean {{exo:container=root}}
> * Once the command is over, go to http://localhost:8080/portal/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-3245) Add comfriming when user remove permissions on edit page & site
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3245?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3245:
----------------------------------
Sprint: Sprint 77, Sprint 78, Sprint 79, Sprint 80 (was: Sprint 77, Sprint 78, Sprint 79)
> Add comfriming when user remove permissions on edit page & site
> ---------------------------------------------------------------
>
> Key: GTNPORTAL-3245
> URL: https://issues.jboss.org/browse/GTNPORTAL-3245
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.1.Final
> Reporter: Hai Nguyen
> Assignee: Hai Nguyen
> Priority: Minor
> Labels: backlogs
> Original Estimate: 4 hours
> Time Spent: 1 day, 7 hours
> Remaining Estimate: 0 minutes
>
> - Login portal
> - Go to user and group management
> - Choose Group management tab
> - Add new group ( ex: AAA)
> - Go to Pages
> - Add new page for group above
> - Search this page and click edit
> - Click view page properties
> - Change access and edit permission to ( organization/*)
> - Click Finish button on Editor composer
> => Unknown error and throw exception in console
> {noformat}
> 2013-08-08 15:20:18,549 | ERROR | Error during the processAction phase [portal:UIPortalApplication<http-nio-0.0.0.0-8080-exec-10>]
> java.lang.NullPointerException: null
> at org.exoplatform.portal.webui.portal.UIPortalComposer$FinishPageEditionActionListener.execute(UIPortalComposer.java:680) ~[exo.portal.webui.portal-3.5.6-PLF.jar:3.5.6-PLF]
>
> {noformat}
>
> Reproduce on edit site is the same
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-2751) <priority> in navigation.xml files ignored for merge importMode
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2751?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2751:
----------------------------------
Sprint: Sprint 77, Sprint 78, Sprint 79, Sprint 80 (was: Sprint 77, Sprint 78, Sprint 79)
> <priority> in navigation.xml files ignored for merge importMode
> ----------------------------------------------------------------
>
> Key: GTNPORTAL-2751
> URL: https://issues.jboss.org/browse/GTNPORTAL-2751
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Trong Tran
> Original Estimate: 4 hours
> Time Spent: 1 day, 2 hours
> Remaining Estimate: 1 hour
>
> Steps to reproduce:
> Clone the Portal Extension Quickstart and deploy it changing the {{<priority>}} value in {{war/src/main/webapp/WEB-INF/conf/sample-ext/portal/group/platform/administrators/navigation.xml}}.
> NOT OK: The changes have no effect, because priority is ignored in {{org.exoplatform.portal.mop.importer.NavigationImporter.perform()}} with {{importMode}} {{merge}}.
> h3. Solution Proposal A
> * Make {{<priority>}} optional in {{gatein_objects}} XSD and {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}}
> * Explicitly state in the documentation [1] that {{<priority>}} is considered only if not already set (first wins).
> h3. Solution Proposal B
> * Make {{<priority>}} optional in {{gatein_objects}} XSD and {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}}
> * Change the behavior of {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}} to the effect that {{<priority>}} is handled in the same way as navigation nodes: it is used or ignored according to the chosen {{importMode}}. Esp. for {{importMode}} {{merge}} the last read {{<priority>}} should win.
> * Document it in [1]
> For both A and B the most or all occutences of {{<priority>}} should be removed from Portal Extension Quickstart.
> [1] [https://docs.jboss.org/author/display/GTNPORTAL35/Portal+Navigation+Confi...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-3044) Inconsistency in html elements of shared layout/user bar portlets
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3044?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3044:
----------------------------------
Sprint: Sprint 77, Sprint 78, Sprint 79, Sprint 80 (was: Sprint 77, Sprint 78, Sprint 79)
> Inconsistency in html elements of shared layout/user bar portlets
> -----------------------------------------------------------------
>
> Key: GTNPORTAL-3044
> URL: https://issues.jboss.org/browse/GTNPORTAL-3044
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta02
> Environment: jboss-jpp-6.1.0.ER1-prod-17052013.zip
> Reporter: Vlastislav Ramik
> Assignee: Tuyen Nguyen The
> Labels: JPP61-Test-dev
> Original Estimate: 6 hours
> Time Spent: 1 day
> Remaining Estimate: 0 minutes
>
> Shared layout/user bar portlets (ie the bar that appears at the top of the page when you are a logged-in user) has following inconsistency:
> Portal Actions (that with the redhat icon): {noformat}<li title="Portal Actions" style="width: 62px" class="UITab portlet-menu-item">{noformat} The is also empty link as a child of the <li> but it has zero length.
> Site: {noformat}<a title="Sites" class="SitesIcon TBIcon" href="javascript:;">Site</a>{noformat}
> Group: {noformat}<span title="Group" class="GroupIcon TBIcon">Group</span>{noformat}
> Dashboard: If the user does not have any dashboard pages there is a link. If the user has a dashboard page there is a span. This is correct in my opinion.
> Site/Group/Dashboard Editor: {noformat}<a title="Site/Group/Dashboard Editor" href="#" class="EditorIcon TBIcon">Site/Group/Dashboard Editor</a>{noformat}
> All this leads to different looking cursors when you hovering the portlet.
> Portal Actions: arrow cursor
> Site: link cursor and text is highlighted
> Group:
> - arrow cursor when you are hovering that "people" icon
> - text cursor when you are hovering Group text
> Dashboard:
> - in case of none dashboard pages - it behaves the same as Site
> - in case on any dashboard pages - it behaves the same as Group
> Site/Group/Dashboard Editor: link cursor and text is highlighted
> The solution can be using css cursor (e.g. cursor: pointer; ) but cleaner solution would be probably unify it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months