[JBoss JIRA] (GTNPORTAL-2713) GateIn doesn't work after reloading AS7
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2713?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2713:
----------------------------------
Sprint: Sprint 77, Sprint 78 (was: Sprint 77)
> GateIn doesn't work after reloading AS7
> ---------------------------------------
>
> Key: GTNPORTAL-2713
> URL: https://issues.jboss.org/browse/GTNPORTAL-2713
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Stian Thorgersen
> Assignee: Hai Nguyen
> Original Estimate: 4 hours
> Time Spent: 5 hours
> Remaining Estimate: 0 minutes
>
> GateIn doesn't work after AS7 has been reloaded (using the management interface).
> Stack trace:
> {code}
> 14:25:48,980 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."gatein.ear".gatein.init: org.jboss.msc.service.StartException in service jboss.deployment.unit."gatein.ear".gatein.init: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
> Caused by: org.picocontainer.defaults.DuplicateComponentKeyRegistrationException: Key class org.gatein.integration.wsrp.plugins.AS7Plugins duplicated
> at org.exoplatform.container.ConcurrentPicoContainer.registerComponent(ConcurrentPicoContainer.java:237)
> at org.exoplatform.container.mc.MCIntegrationContainer.registerComponent(MCIntegrationContainer.java:108)
> at org.exoplatform.container.CachingContainer.registerComponent(CachingContainer.java:174)
> at org.exoplatform.container.ConcurrentPicoContainer.registerComponentInstance(ConcurrentPicoContainer.java:292)
> at org.exoplatform.container.CachingContainer.registerComponentInstance(CachingContainer.java:196)
> at org.exoplatform.container.management.ManageableContainer.registerComponentInstance(ManageableContainer.java:220)
> at org.gatein.integration.jboss.as7.web.InitService.start(InitService.java:66)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> {code}
--
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
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3267) MOP import resource
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3267?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3267:
----------------------------------
Sprint: Sprint 77, Sprint 78 (was: Sprint 77)
> MOP import resource
> -------------------
>
> Key: GTNPORTAL-3267
> URL: https://issues.jboss.org/browse/GTNPORTAL-3267
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Java API
> Affects Versions: 3.5.6.Final
> Reporter: Boubaker Khanfir
> Assignee: Hai Nguyen
> Fix For: 3.5.7.Final
>
> Attachments: portal_mobile_2013-10-01_11-22-50.zip
>
> Original Estimate: 4 hours
> Time Spent: 6 hours
> Remaining Estimate: 0 minutes
>
> MOP resource management is based on a custom marshaller/unmarshaller (org.exoplatform.portal.mop.management.binding.xml.*).
> I had used the mop managed resource in a custom case:
> * Create a new site.
> * Add PortalBody in a container.
> * Export site using GateIN management.
> * Re-import exported site.
> => Exception:
> {code}
> Operation exception for operation import-resource and address /mop [org.gatein.management.cli<pool-4-thread-1>]
> org.gatein.management.api.exceptions.OperationException: Exception reading data for import.
> at org.exoplatform.portal.mop.management.operations.MopImportResource.execute(MopImportResource.java:198) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> at org.gatein.management.core.api.controller.SimpleManagementController.execute(SimpleManagementController.java:100) ~[gatein-management-core-1.1.0.Final.jar:1.1.0.Final]
> ...
> Caused by: org.staxnav.StaxNavException: Unexpected element 'page-body' at [row,col]:[167,21]
> at org.gatein.common.xml.stax.navigator.Exceptions.unexpectedElement(Exceptions.java:45) ~[exo.portal.component.common-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> at org.exoplatform.portal.mop.management.binding.xml.AbstractMarshaller.unmarshalContainer(AbstractMarshaller.java:171) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> at org.exoplatform.portal.mop.management.binding.xml.SiteLayoutMarshaller.unmarshalPortalConfig(SiteLayoutMarshaller.java:216) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> at org.exoplatform.portal.mop.management.binding.xml.SiteLayoutMarshaller.unmarshal(SiteLayoutMarshaller.java:80) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> ... 40 common frames omitted
> {code}
> To fix this I used the *default* MOP marshaller:
> {code}
> import org.exoplatform.portal.config.model.ModelUnmarshaller;
> // ...
> public PortalConfig unmarshal(InputStream inputStream) throws BindingException {
> try {
> return ModelUnmarshaller.unmarshall(PortalConfig.class, inputStream).getObject();
> } catch (Exception e) {
> throw new BindingException(e);
> }
> }
> //...
> public Page.PageSet unmarshal(InputStream inputStream) throws BindingException {
> try {
> return ModelUnmarshaller.unmarshall(Page.PageSet.class, inputStream).getObject();
> } catch (Exception e) {
> throw new BindingException(e);
> }
> }
> //...
> public PageNavigation unmarshal(InputStream inputStream) throws BindingException {
> try {
> return ModelUnmarshaller.unmarshall(PageNavigation.class, inputStream).getObject();
> } catch (Exception e) {
> throw new BindingException(e);
> }
> }
> // ...
> {code}
--
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
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-2542) Wrong name for shared javascript module UIVirtualList.js
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2542?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2542:
----------------------------------
Sprint: Sprint 77, Sprint 78 (was: Sprint 77)
> Wrong name for shared javascript module UIVirtualList.js
> --------------------------------------------------------
>
> Key: GTNPORTAL-2542
> URL: https://issues.jboss.org/browse/GTNPORTAL-2542
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.2.0-GA
> Reporter: Martin Weiler
> Assignee: Tuyen Nguyen The
> Priority: Minor
> Original Estimate: 1 hour
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> https://community.jboss.org/wiki/SharedJavascript lists the following webui-ext modules:
> <script>
> <name>eXo.webui.UIVirtualList</name>
> <path>/javascript/eXo/webui/UIVirtualList.js</path>
> </script>
> <script>
> <name>eXo.webui.UICombobox</name>
> <path>/javascript/eXo/webui/UICombobox.js</path>
> </script>
> In web/eXoResources/src/main/webapp/WEB-INF/gatein-resources.xml, both scripts are using the same identifier 'eXo.webui.UICombobox':
> <param>
> <js-module>eXo.webui.UICombobox</js-module>
> <js-path>/javascript/eXo/webui/UICombobox.js</js-path>
> <js-priority>4</js-priority>
> </param>
> <param>
> <js-module>eXo.webui.UICombobox</js-module>
> <js-path>/javascript/eXo/webui/UIVirtualList.js</js-path>
> <js-priority>4</js-priority>
> </param>
--
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
11 years, 4 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 (was: Sprint 77)
> 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: 6 hours
> 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
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3159) Warn when a PortalContainerDef contains a non-existent dependency.
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3159?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3159:
----------------------------------
Sprint: Sprint 77, Sprint 78 (was: Sprint 77)
> Warn when a PortalContainerDef contains a non-existent dependency.
> ------------------------------------------------------------------
>
> Key: GTNPORTAL-3159
> URL: https://issues.jboss.org/browse/GTNPORTAL-3159
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Vu Viet Phuong
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> This is important in a situation when a developer works on a Portal Extension or custom portal and he includes a non-existent dependency in the configuration of {{org.exoplatform.container.definition.PortalContainerDefinitionPlugin}} in {{configuration.xml}} file.
> Currently, the portal does not complain at all, the resource loading does not work as expected by the developer but he has little chance to track down the problem quickly and effectively. The portal should definitely warn when {{PortalContainerDefinition}} contains a non-existent dependency.
--
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
11 years, 4 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 (was: Sprint 77)
> <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: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Hai Nguyen
> Original Estimate: 4 hours
> Time Spent: 2 hours
> Remaining Estimate: 2 hours
>
> 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
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-2930) Portal keep session alive property values are confusing
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2930?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2930:
----------------------------------
Sprint: Sprint 77, Sprint 78 (was: Sprint 77)
> Portal keep session alive property values are confusing
> -------------------------------------------------------
>
> Key: GTNPORTAL-2930
> URL: https://issues.jboss.org/browse/GTNPORTAL-2930
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta01
> Reporter: Dominik Pospisil
> Assignee: Tuyen Nguyen The
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> According to documentation, portal "keep seesion alive" property values meaning are as follows:
> never - The session will never timeout, even if an application requests it.
> On-demand - The session will timeout if an application requests it
> Always - The session will time out after a set period
> This is quite confusing. E.g. keep session alive never actually means to keep session alive forever.
> Keep session alive always means to let the session timeout automatically.
> If the documentation is correct, the name of the property or property values should be changed.
--
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
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3107) NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3107?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3107:
----------------------------------
Sprint: Sprint 77, Sprint 78 (was: Sprint 77)
> NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
> -----------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3107
> URL: https://issues.jboss.org/browse/GTNPORTAL-3107
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Vu Viet Phuong
> Labels: worked
> Original Estimate: 1 day
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> I am not sure if this is a bug or feature. Anyway, GateIn does not like WARs which do not have {{<display-name>}} in their {{web.xml}}. I guess the portal should be able to work around the non-availabbility of an explicit <display-name> through working with the default one?
> Steps to reproduce:
> * Take any quickstart from https://github.com/gatein/gatein-portal-quickstart, e.g. simplest-hello-world-portlet
> * remove {{<display-name>}} from {{web.xml}}
> * Compile & deploy
> * Expected: The portal should swallow the portlet app without any error.
> * Current: The portal throws this NPE
> {code}
> [0m[31m09:20:11,195 ERROR [org.exoplatform.web.application.javascript.JavascriptConfigDeployer] (ServerService Thread Pool -- 93) An error occurs while registering 'Javascript in gatein-resources.xml' from the context 'null': java.lang.IllegalArgumentException: The context name cannot be null
> at org.exoplatform.container.definition.PortalContainerConfig.getPortalContainerNames(PortalContainerConfig.java:502) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:474) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.add(JavascriptConfigDeployer.java:96) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.onEvent(JavascriptConfigDeployer.java:71) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.gatein.wci.ServletContainer.safeFireEvent(ServletContainer.java:319) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.fireEvent(ServletContainer.java:338) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.access$400(ServletContainer.java:56) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer$RegistrationImpl.registerWebApp(ServletContainer.java:462) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.start(JB7ServletContainerContext.java:369) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.lifecycleEvent(JB7ServletContainerContext.java:223) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3772) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
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
11 years, 4 months