Re: Exception when trying out the fling sample

[Vlad Bailescu]

Hi Roy,

It seems Thymeleaf is not handling the HTML scripts, they get processed by
Sightly instead. You could check the configured service ranking of
Thymeleaf, as suggested in
https://sling.apache.org/documentation/bundles/scripting/scripting-thymeleaf.html

Best,
Vlad

On Saturday, 30 April 2016, Roy Teeuwen  wrote:

> Hello all,
>
> When navigating to fling.html after installing the fling samples I get
> following exception, any thought on what is going wrong?
> Parsing error in template /apps/fling/page/simple/html.html at line 20:
> extraneous input '(' expecting {'}', '.', '&&', '||', '[', '@'} for
> expression
> page=${request.adaptTo(@org.apache.sling.samples.fling.page.Page@class)}
> (500)
>
> The requested URL /fling.html resulted in an error in
> /apps/fling/page/simple/html.html.
>
> Exception:
>
> org.apache.sling.scripting.sightly.SightlyException: Parsing error in
> template /apps/fling/page/simple/html.html at line 20: extraneous input '('
> expecting {'}', '.', '&&', '||', '[', '@'} for expression
> page=${request.adaptTo(@org.apache.sling.samples.fling.page.Page@class)}
> at
> org.apache.sling.scripting.sightly.impl.engine.UnitLoader.getSourceCodeForScript(UnitLoader.java:135)
> at
> org.apache.sling.scripting.sightly.impl.engine.UnitLoader.createUnit(UnitLoader.java:100)
> at
> org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.evaluateScript(SightlyScriptEngine.java:91)
>
> The installed bundles that I am using to get the sample active on the
> current Sling 9-SNAPSHOT launchpad are the following:
>
> 
> org.apache.sling.samples
> org.apache.sling.samples.fling
> 0.0.1-SNAPSHOT
> 
> 
> 
> org.apache.sling
> org.apache.sling.query
> 3.0.0
> 
> 
> 
> org.apache.sling
>
> org.apache.sling.jcr.jackrabbit.usermanager
> 2.2.4
> 
> 
> 
> org.apache.sling
> org.apache.sling.scripting.thymeleaf
> 0.0.6
> 
> 
> org.thymeleaf
> thymeleaf
> 3.0.0.BETA02
> 
> 
> org.apache.sling
> org.apache.sling.i18n
> 2.2.10
> 
> 
> org.javassist
> javassist
> 3.18.2-GA
> 
> 
> commons-io
> commons-io
> 2.4
> 
> 
> org.apache.servicemix.bundles
> org.apache.servicemix.bundles.xerces
> 2.11.0_1
> 
> 
> org.apache.servicemix.bundles
>
> org.apache.servicemix.bundles.xmlresolver
> 1.2_5
> 
> 
> 
> org.apache.sling
> org.apache.sling.validation.api
> 1.0.0-SNAPSHOT
> 
> 
> org.apache.sling
> org.apache.sling.validation.core
> 1.0.0-SNAPSHOT
> 
> 
> 
> org.apache.sling
> org.apache.sling.commons.messaging
> 0.0.1-SNAPSHOT
> 
>
> Greetings,
> Roy



-- 
Sent from mobile

Re: Exception when trying out the fling sample

[Roy Teeuwen]

Hey Vlad,

Thanks. I changed the HTML 5 Template Handler pattern to *.html and the 
Thymeleaf Script Engine Factory service ranking to 150 in the felix config 
manager. But still I get the same error. I don’t see anything about this in the 
docs you sent? Deactivating the sightly engine bundle also fixes it but I would 
rather fix it by configuration when possible of course.

Greets,
Roy
> On 30 Apr 2016, at 19:34, Vlad Bailescu  wrote:
> 
> Hi Roy,
> 
> It seems Thymeleaf is not handling the HTML scripts, they get processed by 
> Sightly instead. You could check the configured service ranking of Thymeleaf, 
> as suggested in 
> https://sling.apache.org/documentation/bundles/scripting/scripting-thymeleaf.html
>  
> 
> 
> Best,
> Vlad
> 
> On Saturday, 30 April 2016, Roy Teeuwen  > wrote:
> Hello all,
> 
> When navigating to fling.html after installing the fling samples I get 
> following exception, any thought on what is going wrong?
> Parsing error in template /apps/fling/page/simple/html.html at line 20: 
> extraneous input '(' expecting {'}', '.', '&&', '||', '[', '@'} for 
> expression 
> page=${request.adaptTo(@org.apache.sling.samples.fling.page.Page@class)} (500)
> 
> The requested URL /fling.html resulted in an error in 
> /apps/fling/page/simple/html.html.
> 
> Exception:
> 
> org.apache.sling.scripting.sightly.SightlyException: Parsing error in 
> template /apps/fling/page/simple/html.html at line 20: extraneous input '(' 
> expecting {'}', '.', '&&', '||', '[', '@'} for expression 
> page=${request.adaptTo(@org.apache.sling.samples.fling.page.Page@class)}
> at 
> org.apache.sling.scripting.sightly.impl.engine.UnitLoader.getSourceCodeForScript(UnitLoader.java:135)
> at 
> org.apache.sling.scripting.sightly.impl.engine.UnitLoader.createUnit(UnitLoader.java:100)
> at 
> org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.evaluateScript(SightlyScriptEngine.java:91)
> 
> The installed bundles that I am using to get the sample active on the current 
> Sling 9-SNAPSHOT launchpad are the following:
> 
> 
> org.apache.sling.samples
> org.apache.sling.samples.fling
> 0.0.1-SNAPSHOT
> 
> 
> 
> org.apache.sling
> org.apache.sling.query
> 3.0.0
> 
> 
> 
> org.apache.sling
> 
> org.apache.sling.jcr.jackrabbit.usermanager
> 2.2.4
> 
> 
> 
> org.apache.sling
> org.apache.sling.scripting.thymeleaf
> 0.0.6
> 
> 
> org.thymeleaf
> thymeleaf
> 3.0.0.BETA02
> 
> 
> org.apache.sling
> org.apache.sling.i18n
> 2.2.10
> 
> 
> org.javassist
> javassist
> 3.18.2-GA
> 
> 
> commons-io
> commons-io
> 2.4
> 
> 
> org.apache.servicemix.bundles
> org.apache.servicemix.bundles.xerces
> 2.11.0_1
> 
> 
> org.apache.servicemix.bundles
> org.apache.servicemix.bundles.xmlresolver
> 1.2_5
> 
> 
> 
> org.apache.sling
> org.apache.sling.validation.api
> 1.0.0-SNAPSHOT
> 
> 
> org.apache.sling
> org.apache.sling.validation.core
> 1.0.0-SNAPSHOT
> 
> 
> 
> org.apache.sling
> org.apache.sling.commons.messaging
> 0.0.1-SNAPSHOT
> 
> 
> Greetings,
> Roy
> 
> 
> -- 
> Sent from mobile

Re: Exception when trying out the fling sample

[Oliver Lietz]

On Saturday 30 April 2016 19:17:34 Roy Teeuwen wrote:
> Hello all,

Hello Roy,

> When navigating to fling.html after installing the fling samples I get
> following exception, any thought on what is going wrong? Parsing error in
> template /apps/fling/page/simple/html.html at line 20: extraneous input '('
> expecting {'}', '.', '&&', '||', '[', '@'} for expression
> page=${request.adaptTo(@org.apache.sling.samples.fling.page.Page@class)}
> (500)

until SLING-4430 is implemented you can run one script engine per extension 
only (service ranking is not honored by Sling's script engine manager, no need 
to try). https://issues.apache.org/jira/browse/SLING-4330

For running the Fling sample you have to deinstall Sightly.

I suggest to use the latest Scripting Thymeleaf snapshot which brings 
Thymeleaf 3.0.0.BETA03 (latest release).

The easiest way to get your dependencies right is to look at Launchpad Karaf 
Features:

https://github.com/apache/sling/blob/trunk/contrib/launchpad/karaf/org.apache.sling.launchpad.karaf-features/src/main/feature/feature.xml

But you don't have to fiddle around with dependencies at all when using 
Launchpad Karaf Features or Distribution – just install sling-launchpad-oak-
tar and sling-samples-fling.

Regards,
O.

> The requested URL /fling.html resulted in an error in
> /apps/fling/page/simple/html.html.
> 
> Exception:
> 
> org.apache.sling.scripting.sightly.SightlyException: Parsing error in
> template /apps/fling/page/simple/html.html at line 20: extraneous input '('
> expecting {'}', '.', '&&', '||', '[', '@'} for expression
> page=${request.adaptTo(@org.apache.sling.samples.fling.page.Page@class)} at
> org.apache.sling.scripting.sightly.impl.engine.UnitLoader.getSourceCodeForS
> cript(UnitLoader.java:135) at
> org.apache.sling.scripting.sightly.impl.engine.UnitLoader.createUnit(UnitLo
> ader.java:100) at
> org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.evaluate
> Script(SightlyScriptEngine.java:91)
> 
> The installed bundles that I am using to get the sample active on the
> current Sling 9-SNAPSHOT launchpad are the following:
> 
>   
> org.apache.sling.samples
> org.apache.sling.samples.fling
> 0.0.1-SNAPSHOT
> 
> 
> 
> org.apache.sling
> org.apache.sling.query
> 3.0.0
> 
> 
> 
> org.apache.sling
>
> org.apache.sling.jcr.jackrabbit.usermanager
> 2.2.4
> 
> 
> 
> org.apache.sling
> org.apache.sling.scripting.thymeleaf
> 0.0.6
> 
> 
> org.thymeleaf
> thymeleaf
> 3.0.0.BETA02
> 
> 
> org.apache.sling
> org.apache.sling.i18n
> 2.2.10
> 
> 
> org.javassist
> javassist
> 3.18.2-GA
> 
> 
> commons-io
> commons-io
> 2.4
> 
> 
> org.apache.servicemix.bundles
> org.apache.servicemix.bundles.xerces
> 2.11.0_1
> 
> 
> org.apache.servicemix.bundles
>
> org.apache.servicemix.bundles.xmlresolver
> 1.2_5
> 
> 
> 
> org.apache.sling
> org.apache.sling.validation.api
> 1.0.0-SNAPSHOT
> 
> 
> org.apache.sling
> org.apache.sling.validation.core
> 1.0.0-SNAPSHOT
> 
> 
> 
> org.apache.sling
> org.apache.sling.commons.messaging
> 0.0.1-SNAPSHOT
> 
> 
> Greetings,
> Roy

Re: Exception when trying out the fling sample

[Vlad Bailescu]

On Saturday, 30 April 2016, Oliver Lietz  wrote:

> (service ranking is not honored by Sling's script engine manager, no need
> to try).


Any idea why this is not a bug?

  https://issues.apache.org/jira/browse/SLING-4330
>
>
I was under the impression SLING-4330 is about using both Sightly and
Thymeleaf in the same running instance; and how to solve which one gets
used on a file/script level.

But for using just one scripting engine (Thymeleaf in this case) for a
given extension we could just use the service ranking.

Best,
Vlad


-- 
Sent from mobile

Re: Exception when trying out the fling sample

[Oliver Lietz]

On Saturday 30 April 2016 22:04:57 Vlad Bailescu wrote:
> On Saturday, 30 April 2016, Oliver Lietz  wrote:
> > (service ranking is not honored by Sling's script engine manager, no need
> > to try).
> 
> Any idea why this is not a bug?

Why do you think it should be a bug?

Sling's Scripting support is built around Java's Scripting API (JSR-223) and 
that was obviously not designed to handle multiple script engines for one 
extension or mime type. So it is a limitation in Java's Scripting API.

>   https://issues.apache.org/jira/browse/SLING-4330
> 
> 
> I was under the impression SLING-4330 is about using both Sightly and
> Thymeleaf in the same running instance; and how to solve which one gets
> used on a file/script level.

Right.

> But for using just one scripting engine (Thymeleaf in this case) for a
> given extension we could just use the service ranking.

What is the benefit?

If you give Thymeleaf's script engine a higher service ranking than Sightly's 
to render HTML templates (.html) you make Sightly quite useless. The result is 
similar to deactivating/deinstalling Sightly's bundles (correct me if I'm 
wrong).

The other way round is not that destructive because Thymeleaf's script engine 
can be configured for different extensions (e.g. .htm, .thtml), can handle not 
only HTML but also XML, CSS, JavaScript, text and raw templates and makes its 
TemplateEngine available as OSGi service to render templates outside of 
Sling's Scripting context (see Fling sample).

So unless SLING-4330 is implemented and you want to use Thymeleaf for .html 
just deinstall Sightly.

Regards,
O.

> Best,
> Vlad

Re: Exception when trying out the fling sample

[Vlad Bailescu]

Hi,

My comments are inline.

On Sunday, 1 May 2016, Oliver Lietz  wrote:

> On Saturday 30 April 2016 22:04:57 Vlad Bailescu wrote:
> > On Saturday, 30 April 2016, Oliver Lietz  > wrote:
> > > (service ranking is not honored by Sling's script engine manager, no
> need
> > > to try).
> >
> > Any idea why this is not a bug?
>
> Why do you think it should be a bug?


Because Sling generally uses the service ranking and it's a great mechanism.


> Sling's Scripting support is built around Java's Scripting API (JSR-223)
> and
> that was obviously not designed to handle multiple script engines for one
> extension or mime type. So it is a limitation in Java's Scripting API.
>

The implementation could use service ranking as an optional/custom
extension of the standard.


> >   https://issues.apache.org/jira/browse/SLING-4330
> >
> >
> > I was under the impression SLING-4330 is about using both Sightly and
> > Thymeleaf in the same running instance; and how to solve which one gets
> > used on a file/script level.
>
> Right.
>
> > But for using just one scripting engine (Thymeleaf in this case) for a
> > given extension we could just use the service ranking.
>
> What is the benefit?
>
> If you give Thymeleaf's script engine a higher service ranking than
> Sightly's
> to render HTML templates (.html) you make Sightly quite useless. The
> result is
> similar to deactivating/deinstalling Sightly's bundles (correct me if I'm
> wrong).
>
> The other way round is not that destructive because Thymeleaf's script
> engine
> can be configured for different extensions (e.g. .htm, .thtml), can handle
> not
> only HTML but also XML, CSS, JavaScript, text and raw templates and makes
> its
> TemplateEngine available as OSGi service to render templates outside of
> Sling's Scripting context (see Fling sample).
>
> So unless SLING-4330 is implemented and you want to use Thymeleaf for .html
> just deinstall Sightly.
>

Right, but that seems a bit counter-intuitive since Sightly ships as
default with Sling. From an user point of view it would make sense to just
bump the ranking of Thymeleaf to make it "cut in front" instead of
uninstalling something.

This will not solve SLING-4330, of course, but will provide a better user
experience, IMO.


> Regards,
> O.


>
Best,
Vlad


-- 
Sent from mobile

Re: Exception when trying out the fling sample

[Oliver Lietz]

On Sunday 01 May 2016 10:05:33 Vlad Bailescu wrote:
> Hi,
> 
> My comments are inline.
> 
> On Sunday, 1 May 2016, Oliver Lietz  wrote:
> > On Saturday 30 April 2016 22:04:57 Vlad Bailescu wrote:
> > > On Saturday, 30 April 2016, Oliver Lietz  > 
> > > wrote:
> > > > (service ranking is not honored by Sling's script engine manager, no
> > 
> > need
> > 
> > > > to try).
> > > 
> > > Any idea why this is not a bug?
> > 
> > Why do you think it should be a bug?
> 
> Because Sling generally uses the service ranking and it's a great mechanism.

"generally" is a somewhat optimistic term when it comes to service ranking at 
Sling. I don't think it's a bug still, but using service ranking could be an 
improvement indeed.

> > Sling's Scripting support is built around Java's Scripting API (JSR-223)
> > and
> > that was obviously not designed to handle multiple script engines for one
> > extension or mime type. So it is a limitation in Java's Scripting API.
> 
> The implementation could use service ranking as an optional/custom
> extension of the standard.

Right. And we will need an extension somehow when script engine manager is 
asked for an engine by extension or mime type. The manager could return null, 
throw an Exception or select the engine by service ranking when more than one 
engine is registered per extension or mime type. It will be implemented as 
part of SLING-4330 (work in progress).

> > >   https://issues.apache.org/jira/browse/SLING-4330
> > > 
> > > I was under the impression SLING-4330 is about using both Sightly and
> > > Thymeleaf in the same running instance; and how to solve which one gets
> > > used on a file/script level.
> > 
> > Right.
> > 
> > > But for using just one scripting engine (Thymeleaf in this case) for a
> > > given extension we could just use the service ranking.
> > 
> > What is the benefit?
> > 
> > If you give Thymeleaf's script engine a higher service ranking than
> > Sightly's
> > to render HTML templates (.html) you make Sightly quite useless. The
> > result is
> > similar to deactivating/deinstalling Sightly's bundles (correct me if I'm
> > wrong).
> > 
> > The other way round is not that destructive because Thymeleaf's script
> > engine
> > can be configured for different extensions (e.g. .htm, .thtml), can handle
> > not
> > only HTML but also XML, CSS, JavaScript, text and raw templates and makes
> > its
> > TemplateEngine available as OSGi service to render templates outside of
> > Sling's Scripting context (see Fling sample).
> > 
> > So unless SLING-4330 is implemented and you want to use Thymeleaf for
> > .html
> > just deinstall Sightly.
> 
> Right, but that seems a bit counter-intuitive since Sightly ships as
> default with Sling. From an user point of view it would make sense to just
> bump the ranking of Thymeleaf to make it "cut in front" instead of
> uninstalling something.

Sling Launchpad ships with Sightly because Adobe is pushing Sightly with full 
force. If you use Sling Launchpad Karaf no Scripting implementation is 
installed at all and you have the freedom to choose.

> This will not solve SLING-4330, of course, but will provide a better user
> experience, IMO.

Patches are welcome, go ahead!

O.

> > Regards,
> > O.
> 
> Best,
> Vlad

Re: Exception when trying out the fling sample

[Roy Teeuwen]

Hey Olivier,

Thanks for the explanation! For me real the benefit would be that I could take 
a vanilla sling launchpad and install the project where I would add a config 
file making the thymeleaf engine a higher service ranking and it would all work 
without any manual action of the user in the system console (unless there is a 
way I don’t know of that you can deactivate bundles through a config / maven 
plugin).

Also I still seem to be getting errors in the fling sample. 

Firstly, when going to the form page, I get following error which can be fixed 
by making the  tags closed in the templates:

org.thymeleaf.exceptions.TemplateInputException: Exception parsing 
document: template="/apps/fling/page/form/html.html", line 52 - column 
Caused by: org.xml.sax.SAXParseException; lineNumber: 52; columnNumber: 
9; The element type "input" must be terminated by the matching end-tag 
"”.

Secondly, when I manually close the input tags myself in the 
/apps/fling/page/form/html.html template and I submit the form, I just get 
redirected to following page and no validation occures:

Content modified /content/fling/validation

Status  200
Message OK
Location/fling/validation
Parent Location /fling
Path/content/fling/validation
Referer http://localhost:8080/fling/validation.html
ChangeLog   
modified("/content/fling/validation/formType");modified("/content/fling/validation/name");
Go Back

Modified Resource

Parent of Modified Resource

Lastly, I was wondering what should be on the sling commons messaging page in 
the example. I just get a page with three columns, subject from and text but 
nothing filled in.

Thanks!
Greetings,
Roy



> On 01 May 2016, at 09:42, Oliver Lietz  wrote:
> 
> On Sunday 01 May 2016 10:05:33 Vlad Bailescu wrote:
>> Hi,
>> 
>> My comments are inline.
>> 
>> On Sunday, 1 May 2016, Oliver Lietz  wrote:
>>> On Saturday 30 April 2016 22:04:57 Vlad Bailescu wrote:
 On Saturday, 30 April 2016, Oliver Lietz >> 
>>> > wrote:
> (service ranking is not honored by Sling's script engine manager, no
>>> 
>>> need
>>> 
> to try).
 
 Any idea why this is not a bug?
>>> 
>>> Why do you think it should be a bug?
>> 
>> Because Sling generally uses the service ranking and it's a great mechanism.
> 
> "generally" is a somewhat optimistic term when it comes to service ranking at 
> Sling. I don't think it's a bug still, but using service ranking could be an 
> improvement indeed.
> 
>>> Sling's Scripting support is built around Java's Scripting API (JSR-223)
>>> and
>>> that was obviously not designed to handle multiple script engines for one
>>> extension or mime type. So it is a limitation in Java's Scripting API.
>> 
>> The implementation could use service ranking as an optional/custom
>> extension of the standard.
> 
> Right. And we will need an extension somehow when script engine manager is 
> asked for an engine by extension or mime type. The manager could return null, 
> throw an Exception or select the engine by service ranking when more than one 
> engine is registered per extension or mime type. It will be implemented as 
> part of SLING-4330 (work in progress).
> 
  https://issues.apache.org/jira/browse/SLING-4330
 
 I was under the impression SLING-4330 is about using both Sightly and
 Thymeleaf in the same running instance; and how to solve which one gets
 used on a file/script level.
>>> 
>>> Right.
>>> 
 But for using just one scripting engine (Thymeleaf in this case) for a
 given extension we could just use the service ranking.
>>> 
>>> What is the benefit?
>>> 
>>> If you give Thymeleaf's script engine a higher service ranking than
>>> Sightly's
>>> to render HTML templates (.html) you make Sightly quite useless. The
>>> result is
>>> similar to deactivating/deinstalling Sightly's bundles (correct me if I'm
>>> wrong).
>>> 
>>> The other way round is not that destructive because Thymeleaf's script
>>> engine
>>> can be configured for different extensions (e.g. .htm, .thtml), can handle
>>> not
>>> only HTML but also XML, CSS, JavaScript, text and raw templates and makes
>>> its
>>> TemplateEngine available as OSGi service to render templates outside of
>>> Sling's Scripting context (see Fling sample).
>>> 
>>> So unless SLING-4330 is implemented and you want to use Thymeleaf for
>>> .html
>>> just deinstall Sightly.
>> 
>> Right, but that seems a bit counter-intuitive since Sightly ships as
>> default with Sling. From an user point of view it would make sense to just
>> bump the ranking of Thymeleaf to make it "cut in front" instead of
>> uninstalling something.
> 
> Sling Launchpad ships with Sightly because Adobe is pushing Sightly with full 
> force. If you use Sling Launchpad Karaf no Scripting implementation is 
> installed a

Re: Exception when trying out the fling sample

[Oliver Lietz]

On Sunday 01 May 2016 11:49:18 Roy Teeuwen wrote:
> Hey Olivier,

Hi Roy,

> Thanks for the explanation! For me real the benefit would be that I could
> take a vanilla sling launchpad and install the project where I would add a
> config file making the thymeleaf engine a higher service ranking and it
> would all work without any manual action of the user in the system console
> (unless there is a way I don’t know of that you can deactivate bundles
> through a config / maven plugin).

I don't think that it is possible right now, but you can build a custom 
Launchpad with Sling's Provisioning Model:

https://sling.apache.org/documentation/development/slingstart.html

> Also I still seem to be getting errors in the fling sample.
> 
> Firstly, when going to the form page, I get following error which can be
> fixed by making the  tags closed in the templates:
> 
>   org.thymeleaf.exceptions.TemplateInputException: Exception parsing
> document: template="/apps/fling/page/form/html.html", line 52 - column
> Caused by: org.xml.sax.SAXParseException; lineNumber: 52; columnNumber: 9;
> The element type "input" must be terminated by the matching end-tag
> "”.

(Thymeleaf 3 is using AttoParser not SAX)

> Secondly, when I manually close the input tags myself in the
> /apps/fling/page/form/html.html template and I submit the form, I just get
> redirected to following page and no validation occures:
> 
>   Content modified /content/fling/validation
> 
>   Status  200
>   Message OK
>   Location/fling/validation
>   Parent Location /fling
>   Path/content/fling/validation
>   Referer http://localhost:8080/fling/validation.html
>   ChangeLog   
modified("/content/fling/validation/formType");modifie
> d("/content/fling/validation/name"); Go Back
> 
>   Modified Resource
> 
>   Parent of Modified Resource

(the FormServlet is not registered as service, ITemplateEngine is missing 
probably)

The Fling sample now makes use of Sling Scripting Thymeleaf's new features so 
please use latest snapshot.

> Lastly, I was wondering what should be on the sling commons messaging page
> in the example. I just get a page with three columns, subject from and text
> but nothing filled in.

If you have installed and configured Commons Messaging Mail you will see mails 
received by (Wiser) SmtpService. For configuration see sling-samples-fling:

https://github.com/apache/sling/blob/trunk/contrib/launchpad/karaf/org.apache.sling.launchpad.karaf-features/src/main/feature/feature.xml

HTH,
O.

> Thanks!
> Greetings,
> Roy
[...]