From issues at jboss.org  Mon Jan 11 21:33:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Mon, 11 Jan 2016 21:33:00 -0500 (EST)
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.36534.1452565980133@Atlassian.JIRA>


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

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)

From issues at jboss.org  Mon Jan 11 21:36:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Mon, 11 Jan 2016 21:36:00 -0500 (EST)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2169) Header values case
	sensitive
In-Reply-To: <JIRA.12449419.1318576380000@Atlassian.JIRA>
References: <JIRA.12449419.1318576380000@Atlassian.JIRA>
	<JIRA.12449419.1318576380000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12449419.1318576380000.36537.1452566160127@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on GTNPORTAL-2169 started by Hai Nguyen.
---------------------------------------------
> Header values case sensitive
> ----------------------------
>
>                 Key: GTNPORTAL-2169
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2169
>             Project: GateIn Portal
>          Issue Type: Feature Request
>          Components: Common integration
>    Affects Versions: 3.1.0-GA, 3.2.0-M01
>            Reporter: Ronny Pscheidl
>            Assignee: Hai Nguyen
>             Fix For: 3.x
>
>
> case sensitiv problem with getHeaders in portal-container.
> For example, if you call request.getHeader("Wicket-Ajax") without portal-container you get the value of this parameter. if you call this in portal-container you get null. in both cases the header value is set. the difference is, that without portal-container you get these parameters by javax.xml.soap.MimeHeaders. it implements getHeader like this with equalsIgnoreCase:
> public String[]  getHeader(String name) {
>          Vector values = new Vector();
>          for(int i = 0; i < headers.size(); i++) {
>             MimeHeader hdr = (MimeHeader) headers.elementAt(i);
>              if (hdr.getName().equalsIgnoreCase(name)
>                  && hdr.getValue() != null)
>                  values.addElement(hdr.getValue());
>          }
>         if (values.size() == 0)
>              return null;
>          String r[] = new String[values.size()];
>          values.copyInto(r);
>          return r;
>      }
> With portal-container you get the header parameter by SimpleMultiValuedProperty method getValue which doesn't ignore case sensetive. so we have to overwrite the method getHeader and getHeaders in our HttpServletRequestWrapper. is there a way to change this in gatein to use also MimeHeaders in PortletRequestImpl instead of SimpleMultiValuedProperty.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Jan 11 21:37:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Mon, 11 Jan 2016 21:37:00 -0500 (EST)
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.36540.1452566220091@Atlassian.JIRA>


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

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)

From issues at jboss.org  Tue Jan 12 05:30:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Tue, 12 Jan 2016 05:30:00 -0500 (EST)
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.37603.1452594600191@Atlassian.JIRA>


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

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)

From issues at jboss.org  Tue Jan 12 05:30:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Tue, 12 Jan 2016 05:30:00 -0500 (EST)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2713) GateIn doesn't work
 after reloading AS7
In-Reply-To: <JIRA.12478911.1352471326000@Atlassian.JIRA>
References: <JIRA.12478911.1352471326000@Atlassian.JIRA>
	<JIRA.12478911.1352471326000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12478911.1352471326000.37604.1452594600214@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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)

From issues at jboss.org  Tue Jan 12 05:35:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Tue, 12 Jan 2016 05:35:00 -0500 (EST)
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.37630.1452594900117@Atlassian.JIRA>


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

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)

From issues at jboss.org  Tue Jan 12 05:48:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Tue, 12 Jan 2016 05:48:00 -0500 (EST)
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.37689.1452595680175@Atlassian.JIRA>


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

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)

From issues at jboss.org  Tue Jan 12 05:54:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Tue, 12 Jan 2016 05:54:00 -0500 (EST)
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.37727.1452596040426@Atlassian.JIRA>


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

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)

From issues at jboss.org  Thu Jan 14 01:06:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Thu, 14 Jan 2016 01:06:00 -0500 (EST)
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.50114.1452751560194@Atlassian.JIRA>


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

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)

From issues at jboss.org  Thu Jan 14 01:12:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Thu, 14 Jan 2016 01:12:00 -0500 (EST)
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.50121.1452751920139@Atlassian.JIRA>


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

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)

From issues at jboss.org  Thu Jan 14 01:36:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Thu, 14 Jan 2016 01:36:00 -0500 (EST)
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.50142.1452753360217@Atlassian.JIRA>


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

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)

From issues at jboss.org  Thu Jan 28 02:41:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Thu, 28 Jan 2016 02:41:00 -0500 (EST)
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.27771.1453966860179@Atlassian.JIRA>


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

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)

From issues at jboss.org  Thu Jan 28 03:53:00 2016
From: issues at jboss.org (Hai Nguyen (JIRA))
Date: Thu, 28 Jan 2016 03:53:00 -0500 (EST)
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.27939.1453971180214@Atlassian.JIRA>


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

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)