August 2013 - gatein-issues - Jboss List Archives

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

by Marko Strukelj (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3248?page=com.atlassian.jira.pl... ] Marko Strukelj updated GTNPORTAL-3248: -------------------------------------- Git Pull Request: https://github.com/gatein/gatein-portal/pull/638, https://github.com/gatein/gatein-portal/pull/635 (was: https://github.com/gatein/gatein-portal/pull/635) > 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 > Attachments: js-modular-reproducer.zip > > > 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3253) [IE] Ajax requests are broken if the node name containing accent characters

by Trong Tran (JIRA)

Trong Tran created GTNPORTAL-3253: ------------------------------------- Summary: [IE] Ajax requests are broken if the node name containing accent characters Key: GTNPORTAL-3253 URL: https://issues.jboss.org/browse/GTNPORTAL-3253 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Environment: Internet Explorer browser Reporter: Trong Tran Priority: Critical h3. Problem Let's say we have a page with node name is "tét". Go to Edit Page, then click on the close/save button ==> it doesn't work. h3. Cause The encoded URI in the href attribute of <a> tag is automatically decoded in wrong ISO-8859-1 before the javascript function is executed h3. Proposal to fix the problem We should use *onclick* to perform the javascript ajax update execution instead of href attribute. Moreover, putting javascript code into href is kind of bad practice that we could avoid in use -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3252) Add new page wizard doesn't remember page layout

by Peter Palaga (JIRA)

Peter Palaga created GTNPORTAL-3252: --------------------------------------- Summary: Add new page wizard doesn't remember page layout Key: GTNPORTAL-3252 URL: https://issues.jboss.org/browse/GTNPORTAL-3252 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Peter Palaga Assignee: Peter Palaga -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2687) Improve Maven Build of Sample Portal and Extension

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2687?page=com.atlassian.jira.pl... ] Peter Palaga resolved GTNPORTAL-2687. ------------------------------------- Resolution: Deferred > Improve Maven Build of Sample Portal and Extension > -------------------------------------------------- > > Key: GTNPORTAL-2687 > URL: https://issues.jboss.org/browse/GTNPORTAL-2687 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > > (1) Config projects > Maven jar packager does not include > src/main/java/conf/configuration.xml > This is a problem in both portal and extension config projects. > conf/configuration.xml needs to be moved from src/main/java to > src/main/resources > (2) EAR > (2.1) Delete src/main/application/META-INF/gatein-jboss-beans.xml > (2.2) Move MANIFEST.MF from > > packaging/jboss-as7/pkg/src/main/resources/jboss/samples/gatein/extensions/*/META-INF > to src/main/resources of the respective projects and configure > maven-ear-plugin to use > <manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile> > (2.3) remove the two application.xml files from > > packaging/jboss-as7/pkg/src/main/resources/jboss/samples/gatein/extensions/*/META-INF > and configure maven-ear-plugin to reach the same result which can be > done very easily. > (2.4) Adjust the the ant code in > packaging/jboss-as7/pkg/package.xml > to the changes done in (2.3) and (2.4). > Open question: > * Is it OK to make the GateIn build process to use EAR archives instead > of *.ear directories to deploy the samples? -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3247) [IE8] Impossible to edit page containing accent character in its name

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3247?page=com.atlassian.jira.pl... ] Trong Tran reassigned GTNPORTAL-3247: ------------------------------------- Assignee: Trong Tran (was: Son Tran) > [IE8] Impossible to edit page containing accent character in its name > --------------------------------------------------------------------- > > Key: GTNPORTAL-3247 > URL: https://issues.jboss.org/browse/GTNPORTAL-3247 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Son Tran > Assignee: Trong Tran > Priority: Minor > Labels: backlogs > Fix For: 3.7.0.Final > > > Using *IE8*, it's not possible to edit a page that contains an accented character in its name. > Try to follow these steps to reproduce: > - login to acme site. > - Edit-> Page-> Add page > - put the name " accentué" > - Save the page, it is created and accessible (navigate to the page) > - Select Edit-> Page-> Layout => nothing happens. > we can not edit the page . > With chrome and FF this works well. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3247) [IE8] Impossible to edit page containing accent character in its name

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3247?page=com.atlassian.jira.pl... ] Trong Tran resolved GTNPORTAL-3247. ----------------------------------- Fix Version/s: 3.7.0.Final Resolution: Done > [IE8] Impossible to edit page containing accent character in its name > --------------------------------------------------------------------- > > Key: GTNPORTAL-3247 > URL: https://issues.jboss.org/browse/GTNPORTAL-3247 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Son Tran > Assignee: Son Tran > Priority: Minor > Labels: backlogs > Fix For: 3.7.0.Final > > > Using *IE8*, it's not possible to edit a page that contains an accented character in its name. > Try to follow these steps to reproduce: > - login to acme site. > - Edit-> Page-> Add page > - put the name " accentué" > - Save the page, it is created and accessible (navigate to the page) > - Select Edit-> Page-> Layout => nothing happens. > we can not edit the page . > With chrome and FF this works well. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3247) [IE8] Impossible to edit page containing accent character in its name

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3247?page=com.atlassian.jira.pl... ] Trong Tran commented on GTNPORTAL-3247: --------------------------------------- The problem also happens in IE9 > [IE8] Impossible to edit page containing accent character in its name > --------------------------------------------------------------------- > > Key: GTNPORTAL-3247 > URL: https://issues.jboss.org/browse/GTNPORTAL-3247 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Son Tran > Assignee: Son Tran > Priority: Minor > Labels: backlogs > > Using *IE8*, it's not possible to edit a page that contains an accented character in its name. > Try to follow these steps to reproduce: > - login to acme site. > - Edit-> Page-> Add page > - put the name " accentué" > - Save the page, it is created and accessible (navigate to the page) > - Select Edit-> Page-> Layout => nothing happens. > we can not edit the page . > With chrome and FF this works well. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3249) Update version.compiler.plugin and jboss.maven.plugin versions in the quickstart POM files

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3249?page=com.atlassian.jira.pl... ] Peter Palaga resolved GTNPORTAL-3249. ------------------------------------- Fix Version/s: 3.6.3.Final Resolution: Done Thanks for PR, Sande! > Update version.compiler.plugin and jboss.maven.plugin versions in the quickstart POM files > ------------------------------------------------------------------------------------------ > > Key: GTNPORTAL-3249 > URL: https://issues.jboss.org/browse/GTNPORTAL-3249 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Sande Gilda > Assignee: Peter Palaga > Fix For: 3.6.3.Final > > > Update the following property versions in the quickstart POM files: > version.jboss.maven.plugin: from 7.3.Final to 7.4.Final > version.compiler.plugin: from 2.3.1 to 3.1 -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3210) Quickstart names in the POM files are often are not clear across products

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3210?page=com.atlassian.jira.pl... ] Peter Palaga resolved GTNPORTAL-3210. ------------------------------------- Resolution: Rejected I thought about this once again and I ended up holding the position that "portlet" or "portal" in {{<artifactId>}}'s and {{<name>}}'s of our quickstarts makes clear enough that they are related to Portal product, thus rejecting this request. > Quickstart names in the POM files are often are not clear across products > ------------------------------------------------------------------------- > > Key: GTNPORTAL-3210 > URL: https://issues.jboss.org/browse/GTNPORTAL-3210 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Sande Gilda > Assignee: Peter Palaga > > Now that we aggregate quickstarts from different repositories and for different products, we need a better way to identify them. We often have quickstarts with the same name in different repositories. > When you run `mvn clean install '-Pdefault,!complex-dependencies'` from the root directory of the quickstarts, it often is not clear which quickstart is compiling. > As described in the CONTRIBUTING.md file, we would like the <name> in the quickstart pom.xml file to follow the template: > JBoss <target-product> Quickstart: <quickstart-name> < - optional-subfolder-name> where target-product is the Target Product metadata specified in the README.md file, quickstart-name is the quickstart folder name, and optional-subfolder-name is the name of any nested subfolder containing a pom.xml file. > This means the Portal cdi-generic-portlet would be: > <name>JBoss JPP Quickstart: cdi-generic-portlet</name> > I know you have concerns about changing this and we can certainly discuss 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2869) TestTransientTokenService tests fails in Java 7

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2869?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-2869: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > TestTransientTokenService tests fails in Java 7 > ----------------------------------------------- > > Key: GTNPORTAL-2869 > URL: https://issues.jboss.org/browse/GTNPORTAL-2869 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Scavelli > Assignee: Peter Palaga > > testCleanExpiredTokens does not delete tokens it has added, making other tests that rely on the size of tokens in the service fail when ran out of order (aka using Java 7). -- 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

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues August 2013