December 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3340) Resource bundle Warnings in Application Registry

by Peter Palaga (JIRA)

Peter Palaga created GTNPORTAL-3340: --------------------------------------- Summary: Resource bundle Warnings in Application Registry Key: GTNPORTAL-3340 URL: https://issues.jboss.org/browse/GTNPORTAL-3340 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.6.3.Final Reporter: Peter Palaga Steps to reproduce: (1) Login as root (2) Visit http://127.0.0.1:8080/portal/g/:platform:administrators/administration/re... (3) NOT OK: There are warnigs in the log: {code} WARN [portal:WebuiBindingContext] (http--0.0.0.0-8180-1) Can not find resource bundle for key : uniq-5b8e7bb6-8b8e-4e39-9204-948a2d598d90.action.title.Delete WARN [portal:WebuiBindingContext] (http--0.0.0.0-8180-1) Can not find resource bundle for key : uniq-5b8e7bb6-8b8e-4e39-9204-948a2d598d90.action.title.Delete WARN [portal:WebuiBindingContext] (http--0.0.0.0-8180-1) Can not find resource bundle for key : uniq-5b8e7bb6-8b8e-4e39-9204.title.ListPermissionSelector {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2394) The GadgetDeployer should unregister itself as WebAppListener in the stop method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2394?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2394: ---------------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 987708|https://bugzilla.redhat.com/show_bug.cgi?id=987708] from ASSIGNED to VERIFIED > The GadgetDeployer should unregister itself as WebAppListener in the stop method > -------------------------------------------------------------------------------- > > Key: GTNPORTAL-2394 > URL: https://issues.jboss.org/browse/GTNPORTAL-2394 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.1.0-GA > Reporter: Nicolas Filotto > Labels: gadget > Fix For: 3.6.4.Final, 3.7.0.Final > > Attachments: GTNPORTAL-2394.patch > > > Up to now, when the application tries to stop the component instead of unregistering itself it registers itself another time. Indeed the current code is: > {code} > public void stop() > { > DefaultServletContainerFactory.getInstance().getServletContainer().addWebAppListener(this); > } > {code} > But should be: > {code} > public void stop() > { > DefaultServletContainerFactory.getInstance().getServletContainer().removeWebAppListener(this); > } > {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3250) The portlets cannot be displayed after a portal reload

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3250?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3250: ---------------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 987708|https://bugzilla.redhat.com/show_bug.cgi?id=987708] from ASSIGNED to VERIFIED > 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 > Fix For: 3.6.4.Final, 3.7.0.Final > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3248) Portlet archive containing gatein-resources.xml fails to redeploy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3248?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3248: ---------------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 987708|https://bugzilla.redhat.com/show_bug.cgi?id=987708] from ASSIGNED to VERIFIED > Portlet archive containing gatein-resources.xml fails to redeploy > ----------------------------------------------------------------- > > Key: GTNPORTAL-3248 > URL: https://issues.jboss.org/browse/GTNPORTAL-3248 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.1.Final > Reporter: Marko Strukelj > Assignee: Vu Viet Phuong > Labels: backlogs > Fix For: 3.7.0.Final > > Attachments: js-modular-reproducer.zip > > Original Estimate: 4 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > During hot redeploy of portlet application JavascripConfigDeployer should remove any resource ids registered during application deploy as a result of using gatein-resources.xml. Logic for that is missing, and we get a duplicate resource id exception: > 19:34:39,162 ERROR [org.exoplatform.web.application.javascript.JavascriptConfigDeployer] (ServerService Thread Pool -- 23) An error occurs while processing 'Javascript in gatein-resources.xml' from the context 'TestJS': java.lang.IllegalStateException: Duplicate ResourceId : PORTLET/js-modular-issue/JSModuleReproducer, later resource definition will be ignored > at org.gatein.portal.controller.resource.script.ScriptGraph.addResource(ScriptGraph.java:223) [exo.portal.component.web.resources-3.6.2.Final-SNAPSHOT.jar:3.6.2.Final-SNAPSHOT] > at org.exoplatform.web.application.javascript.JavascriptTask.execute(JavascriptTask.java:49) [exo.portal.component.web.resources-3.6.2.Final-SNAPSHOT.jar:3.6.2.Final-SNAPSHOT] > at org.exoplatform.web.application.javascript.JavascriptConfigParser.processConfigResource(JavascriptConfigParser.java:124) [exo.portal.component.web.resources-3.6.2.Final-SNAPSHOT.jar:3.6.2.Final-SNAPSHOT] > at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.register(JavascriptConfigDeployer.java:113) [exo.portal.component.web.resources-3.6.2.Final-SNAPSHOT.jar:3.6.2.Final-SNAPSHOT] > at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.access$000(JavascriptConfigDeployer.java:43) [exo.portal.component.web.resources-3.6.2.Final-SNAPSHOT.jar:3.6.2.Final-SNAPSHOT] > at org.exoplatform.web.application.javascript.JavascriptConfigDeployer$1.execute(JavascriptConfigDeployer.java:92) [exo.portal.component.web.resources-3.6.2.Final-SNAPSHOT.jar:3.6.2.Final-SNAPSHOT] > at org.exoplatform.container.RootContainer$PortalContainerPostInitTask.onAlreadyExists(RootContainer.java:1299) [exo.kernel.container-2.4.4-GA.jar:2.4.4-GA] > at org.exoplatform.container.RootContainer.addInitTask(RootContainer.java:1127) [exo.kernel.container-2.4.4-GA.jar:2.4.4-GA] > at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:485) [exo.kernel.container-2.4.4-GA.jar:2.4.4-GA] > at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.add(JavascriptConfigDeployer.java:96) [exo.portal.component.web.resources-3.6.2.Final-SNAPSHOT.jar:3.6.2.Final-SNAPSHOT] > at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.onEvent(JavascriptConfigDeployer.java:71) [exo.portal.component.web.resources-3.6.2.Final-SNAPSHOT.jar:3.6.2.Final-SNAPSHOT] > at org.gatein.wci.ServletContainer.safeFireEvent(ServletContainer.java:319) [wci-wci-2.3.1.Final.jar:2.3.1.Final] > at org.gatein.wci.ServletContainer.fireEvent(ServletContainer.java:338) [wci-wci-2.3.1.Final.jar:2.3.1.Final] > at org.gatein.wci.ServletContainer.access$400(ServletContainer.java:56) [wci-wci-2.3.1.Final.jar:2.3.1.Final] > at org.gatein.wci.ServletContainer$RegistrationImpl.registerWebApp(ServletContainer.java:462) [wci-wci-2.3.1.Final.jar:2.3.1.Final] > at org.gatein.wci.jboss.JB7ServletContainerContext.start(JB7ServletContainerContext.java:369) [wci-jboss7-2.3.1.Final.jar:2.3.1.Final] > at org.gatein.wci.jboss.JB7ServletContainerContext.lifecycleEvent(JB7ServletContainerContext.java:223) [wci-jboss7-2.3.1.Final.jar:2.3.1.Final] > 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:439) [classes.jar:1.6.0_51] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_51] > at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_51] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_51] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > 19:34:39,168 ERROR [org.exoplatform.commons.xml.XMLValidator] (ServerService Thread Pool -- 23) Error in document jndi:/default-host/js-modular-issue/WEB-INF/gatein-resources.xml at (4,89) :cvc-elt.1: Cannot find the declaration of element 'gatein-resources'. > 19:34:39,179 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "js-modular-issue.war" with deployment "js-modular-issue.war" > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3339) Upgrade PortletBridge to the version 3.3.1.Final

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3339?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3339: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/726 > Upgrade PortletBridge to the version 3.3.1.Final > ------------------------------------------------ > > Key: GTNPORTAL-3339 > URL: https://issues.jboss.org/browse/GTNPORTAL-3339 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.6.4.Final, 3.7.0.Final > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3339) Upgrade PortletBridge to the version 3.3.1.Final

by Peter Palaga (JIRA)

Peter Palaga created GTNPORTAL-3339: --------------------------------------- Summary: Upgrade PortletBridge to the version 3.3.1.Final Key: GTNPORTAL-3339 URL: https://issues.jboss.org/browse/GTNPORTAL-3339 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Peter Palaga Assignee: Peter Palaga Fix For: 3.6.4.Final, 3.7.0.Final -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3334) Can edit portlet when Container tab chosen

by Vu Viet Phuong (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3334?page=com.atlassian.jira.pl... ] Vu Viet Phuong updated GTNPORTAL-3334: -------------------------------------- Status: Open (was: Pull Request Sent) > Can edit portlet when Container tab chosen > ------------------------------------------ > > Key: GTNPORTAL-3334 > URL: https://issues.jboss.org/browse/GTNPORTAL-3334 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Hai Nguyen > Fix For: 3.7.0.Final > > Original Estimate: 1 hour > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > - Login portal > - Choose a page > - Click Site Editor > Edit Page > - View page properties > Click Save > - After that, drag & drop a container > - Click Finish button > - Select other page > - Click edit page > => Can edit portlet when choose tab container in Edit Inline composer -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3334) Can edit portlet when Container tab chosen

by Vu Viet Phuong (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3334?page=com.atlassian.jira.pl... ] Vu Viet Phuong commented on GTNPORTAL-3334: ------------------------------------------- I can also reproduce this bug by clicking on Abort edit instead of Finish edit button It'd be better to fix that case also > Can edit portlet when Container tab chosen > ------------------------------------------ > > Key: GTNPORTAL-3334 > URL: https://issues.jboss.org/browse/GTNPORTAL-3334 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Hai Nguyen > Fix For: 3.7.0.Final > > Original Estimate: 1 hour > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > - Login portal > - Choose a page > - Click Site Editor > Edit Page > - View page properties > Click Save > - After that, drag & drop a container > - Click Finish button > - Select other page > - Click edit page > => Can edit portlet when choose tab container in Edit Inline composer -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3333) An attempt to reset the password of a disabled user should fail

by Tuyen Nguyen The (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3333?page=com.atlassian.jira.pl... ] Tuyen Nguyen The commented on GTNPORTAL-3333: --------------------------------------------- as mentioned on issue: https://issues.jboss.org/browse/GTNPORTAL-3326 We should fix also for case: In case user has received the "reset password email" from portal, and he is opening the reset password window, but in that time, an Admin set him disabled, then when that user try to click save --> DisabledUserException > An attempt to reset the password of a disabled user should fail > --------------------------------------------------------------- > > Key: GTNPORTAL-3333 > URL: https://issues.jboss.org/browse/GTNPORTAL-3333 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Hai Nguyen > Fix For: 3.7.0.Final > > Original Estimate: 1 hour > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > An attempt to reset the password of a disabled user should fail with the following message : This user account is disabled. Impossible to reset the password. > Today, the message is mixed both non-existed user and disabled user cases -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3250) The portlets cannot be displayed after a portal reload

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3250?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3250: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 987708|https://bugzilla.redhat.com/show_bug.cgi?id=987708] from ON_QA to ASSIGNED > 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 > Fix For: 3.6.4.Final, 3.7.0.Final > > 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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues December 2013