2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues May 2016

gatein-issues@lists.jboss.org

1 participants
24 discussions

Start a nNew thread

[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)

8 years, 7 months

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)

8 years, 7 months

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)

8 years, 7 months

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)

8 years, 7 months

1
0
0 / 0

← Newer
1
2
3
Older →