Guillaume Nodet commented on KARAF-4707:

I think for url handlers, it's better to use the uber jars.  The urls handlers 
integrate tightly into the framework / VM in an usual way and used without much 
way to actually "wait" for them, unlike plain OSGi services.
I'd rather avoid having url handlers depend on too many things, as it may 
become the target of a refresh for an unneeded reason and increase the risk of 
entering an unwanted state.  In particular, url handlers are used by the 
feature service, usually as prerequisite features to install bundles using 
those urls.  
So I'm all for having features for those handlers, but not really one 
installing all the small bundles.

Also, we already have builtin support for the main 3 ones: mvn, wrap and war 
(through pax-web). All of them are using the uber bundles.

> Add pax-url-classpath feature
> -----------------------------
>                 Key: KARAF-4707
>                 URL: https://issues.apache.org/jira/browse/KARAF-4707
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-feature
>            Reporter: Alex Soto
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.1.0, 4.0.8
> To make it easier to use class path URLs.  Something like.
> {code:xml}
> <feature name="pax-url-handler">
>       <bundle>mvn:org.ops4j.base/ops4j-base-util-property/1.5.0</bundle>
>         <bundle>mvn:org.ops4j.base/ops4j-base-lang/1.5.0</bundle>
>       <bundle>mvn:org.ops4j.pax.swissbox/pax-swissbox-property/1.8.2</bundle>
>         <bundle>mvn:org.ops4j.pax.url/pax-url-commons/2.4.7</bundle>
>         <bundle>mvn:org.ops4j.pax.url/pax-url-classpath/2.4.7</bundle>
> </feature>
> {code}
> Also, it would be nice to have documentation about how to use it for 
> deploying config files in features.xml:
> {code:xml}
> <configfile finalname="${karaf.etc}/my.config.cfg">
>       classpath:my.config.cfg
> </configfile>
> {code}

This message was sent by Atlassian JIRA

Reply via email to