January 2016 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3258) Allow classpath resolver to accept a leading slash

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3258: --------------------------------------- This issues has fixed > Allow classpath resolver to accept a leading slash > -------------------------------------------------- > > Key: GTNPORTAL-3258 > URL: https://issues.jboss.org/browse/GTNPORTAL-3258 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Hai Nguyen > Assignee: Hai Nguyen > Priority: Minor > Fix For: 3.7.0.Final > > > Classpath Resolver for resources does not currently support a leading slash. So for example in a webui component I can't put (or my template won't be found) : > {code} > @ComponentConfig ( > template = "classpath:/path/oto/my/template/MyTemplate.gtmpl", > events = { > } > ) > {code} > whereas this notation is allowed in kernel configuration. For example I can do : > {code} > <import>classpath:/path/to/my/configuration/file/my-configuration.xml</import> > {code} > and it is also allowed in the "app" resolver (I can do "app:/path/oto/my/template/MyTemplate.gtmpl"). > It would be more consistent and less error-prone for the developer to allow to add a leading slash for the classpath resolver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3258) Allow classpath resolver to accept a leading slash

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3258: --------------------------------------- This issues has fixed > Allow classpath resolver to accept a leading slash > -------------------------------------------------- > > Key: GTNPORTAL-3258 > URL: https://issues.jboss.org/browse/GTNPORTAL-3258 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Hai Nguyen > Assignee: Hai Nguyen > Priority: Minor > Fix For: 3.7.0.Final > > > Classpath Resolver for resources does not currently support a leading slash. So for example in a webui component I can't put (or my template won't be found) : > {code} > @ComponentConfig ( > template = "classpath:/path/oto/my/template/MyTemplate.gtmpl", > events = { > } > ) > {code} > whereas this notation is allowed in kernel configuration. For example I can do : > {code} > <import>classpath:/path/to/my/configuration/file/my-configuration.xml</import> > {code} > and it is also allowed in the "app" resolver (I can do "app:/path/oto/my/template/MyTemplate.gtmpl"). > It would be more consistent and less error-prone for the developer to allow to add a leading slash for the classpath resolver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3258) Allow classpath resolver to accept a leading slash

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3258: --------------------------------------- This issues has fixed > Allow classpath resolver to accept a leading slash > -------------------------------------------------- > > Key: GTNPORTAL-3258 > URL: https://issues.jboss.org/browse/GTNPORTAL-3258 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Hai Nguyen > Assignee: Hai Nguyen > Priority: Minor > Fix For: 3.7.0.Final > > > Classpath Resolver for resources does not currently support a leading slash. So for example in a webui component I can't put (or my template won't be found) : > {code} > @ComponentConfig ( > template = "classpath:/path/oto/my/template/MyTemplate.gtmpl", > events = { > } > ) > {code} > whereas this notation is allowed in kernel configuration. For example I can do : > {code} > <import>classpath:/path/to/my/configuration/file/my-configuration.xml</import> > {code} > and it is also allowed in the "app" resolver (I can do "app:/path/oto/my/template/MyTemplate.gtmpl"). > It would be more consistent and less error-prone for the developer to allow to add a leading slash for the classpath resolver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3258) Allow classpath resolver to accept a leading slash

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3258: --------------------------------------- This issues has fixed > Allow classpath resolver to accept a leading slash > -------------------------------------------------- > > Key: GTNPORTAL-3258 > URL: https://issues.jboss.org/browse/GTNPORTAL-3258 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Hai Nguyen > Assignee: Hai Nguyen > Priority: Minor > Fix For: 3.7.0.Final > > > Classpath Resolver for resources does not currently support a leading slash. So for example in a webui component I can't put (or my template won't be found) : > {code} > @ComponentConfig ( > template = "classpath:/path/oto/my/template/MyTemplate.gtmpl", > events = { > } > ) > {code} > whereas this notation is allowed in kernel configuration. For example I can do : > {code} > <import>classpath:/path/to/my/configuration/file/my-configuration.xml</import> > {code} > and it is also allowed in the "app" resolver (I can do "app:/path/oto/my/template/MyTemplate.gtmpl"). > It would be more consistent and less error-prone for the developer to allow to add a leading slash for the classpath resolver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3258) Allow classpath resolver to accept a leading slash

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3258: --------------------------------------- This issues has fixed > Allow classpath resolver to accept a leading slash > -------------------------------------------------- > > Key: GTNPORTAL-3258 > URL: https://issues.jboss.org/browse/GTNPORTAL-3258 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Hai Nguyen > Assignee: Hai Nguyen > Priority: Minor > Fix For: 3.7.0.Final > > > Classpath Resolver for resources does not currently support a leading slash. So for example in a webui component I can't put (or my template won't be found) : > {code} > @ComponentConfig ( > template = "classpath:/path/oto/my/template/MyTemplate.gtmpl", > events = { > } > ) > {code} > whereas this notation is allowed in kernel configuration. For example I can do : > {code} > <import>classpath:/path/to/my/configuration/file/my-configuration.xml</import> > {code} > and it is also allowed in the "app" resolver (I can do "app:/path/oto/my/template/MyTemplate.gtmpl"). > It would be more consistent and less error-prone for the developer to allow to add a leading slash for the classpath resolver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3258) Allow classpath resolver to accept a leading slash

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3258: --------------------------------------- This issues has fixed > Allow classpath resolver to accept a leading slash > -------------------------------------------------- > > Key: GTNPORTAL-3258 > URL: https://issues.jboss.org/browse/GTNPORTAL-3258 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Hai Nguyen > Assignee: Hai Nguyen > Priority: Minor > Fix For: 3.7.0.Final > > > Classpath Resolver for resources does not currently support a leading slash. So for example in a webui component I can't put (or my template won't be found) : > {code} > @ComponentConfig ( > template = "classpath:/path/oto/my/template/MyTemplate.gtmpl", > events = { > } > ) > {code} > whereas this notation is allowed in kernel configuration. For example I can do : > {code} > <import>classpath:/path/to/my/configuration/file/my-configuration.xml</import> > {code} > and it is also allowed in the "app" resolver (I can do "app:/path/oto/my/template/MyTemplate.gtmpl"). > It would be more consistent and less error-prone for the developer to allow to add a leading slash for the classpath resolver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3258) Allow classpath resolver to accept a leading slash

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3258: --------------------------------------- This issues has fixed > Allow classpath resolver to accept a leading slash > -------------------------------------------------- > > Key: GTNPORTAL-3258 > URL: https://issues.jboss.org/browse/GTNPORTAL-3258 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Hai Nguyen > Assignee: Hai Nguyen > Priority: Minor > Fix For: 3.7.0.Final > > > Classpath Resolver for resources does not currently support a leading slash. So for example in a webui component I can't put (or my template won't be found) : > {code} > @ComponentConfig ( > template = "classpath:/path/oto/my/template/MyTemplate.gtmpl", > events = { > } > ) > {code} > whereas this notation is allowed in kernel configuration. For example I can do : > {code} > <import>classpath:/path/to/my/configuration/file/my-configuration.xml</import> > {code} > and it is also allowed in the "app" resolver (I can do "app:/path/oto/my/template/MyTemplate.gtmpl"). > It would be more consistent and less error-prone for the developer to allow to add a leading slash for the classpath resolver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3258) Allow classpath resolver to accept a leading slash

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3258: --------------------------------------- This issues has fixed > Allow classpath resolver to accept a leading slash > -------------------------------------------------- > > Key: GTNPORTAL-3258 > URL: https://issues.jboss.org/browse/GTNPORTAL-3258 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Hai Nguyen > Assignee: Hai Nguyen > Priority: Minor > Fix For: 3.7.0.Final > > > Classpath Resolver for resources does not currently support a leading slash. So for example in a webui component I can't put (or my template won't be found) : > {code} > @ComponentConfig ( > template = "classpath:/path/oto/my/template/MyTemplate.gtmpl", > events = { > } > ) > {code} > whereas this notation is allowed in kernel configuration. For example I can do : > {code} > <import>classpath:/path/to/my/configuration/file/my-configuration.xml</import> > {code} > and it is also allowed in the "app" resolver (I can do "app:/path/oto/my/template/MyTemplate.gtmpl"). > It would be more consistent and less error-prone for the developer to allow to add a leading slash for the classpath resolver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2713) GateIn doesn't work after reloading AS7

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2713?page=com.atlassian.jira.pl... ] Work on GTNPORTAL-2713 started by Hai Nguyen. --------------------------------------------- > GateIn doesn't work after reloading AS7 > --------------------------------------- > > Key: GTNPORTAL-2713 > URL: https://issues.jboss.org/browse/GTNPORTAL-2713 > Project: GateIn Portal > Issue Type: Bug > Reporter: Stian Thorgersen > Assignee: Hai Nguyen > Original Estimate: 4 hours > Time Spent: 5 hours > Remaining Estimate: 1 day > > 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 was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3258) Allow classpath resolver to accept a leading slash

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3258: --------------------------------------- This issues has fixed > Allow classpath resolver to accept a leading slash > -------------------------------------------------- > > Key: GTNPORTAL-3258 > URL: https://issues.jboss.org/browse/GTNPORTAL-3258 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Hai Nguyen > Assignee: Hai Nguyen > Priority: Minor > Fix For: 3.7.0.Final > > > Classpath Resolver for resources does not currently support a leading slash. So for example in a webui component I can't put (or my template won't be found) : > {code} > @ComponentConfig ( > template = "classpath:/path/oto/my/template/MyTemplate.gtmpl", > events = { > } > ) > {code} > whereas this notation is allowed in kernel configuration. For example I can do : > {code} > <import>classpath:/path/to/my/configuration/file/my-configuration.xml</import> > {code} > and it is also allowed in the "app" resolver (I can do "app:/path/oto/my/template/MyTemplate.gtmpl"). > It would be more consistent and less error-prone for the developer to allow to add a leading slash for the classpath resolver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues January 2016