From issues at jboss.org  Fri Mar 18 03:22:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Fri, 18 Mar 2016 03:22:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3258) Allow classpath
 resolver to accept a leading slash
In-Reply-To: <JIRA.12499894.1378286207000@Atlassian.JIRA>
References: <JIRA.12499894.1378286207000@Atlassian.JIRA>
	<JIRA.12499894.1378286207000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12499894.1378286207000.24474.1458285720118@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNPORTAL-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178798#comment-13178798 ] 

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)