karaf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anierb...@apache.org
Subject svn commit: r1102113 - /karaf/trunk/manual/src/main/webapp/users-guide/provisioning.conf
Date Wed, 11 May 2011 22:19:19 GMT
Author: anierbeck
Date: Wed May 11 22:19:19 2011
New Revision: 1102113

URL: http://svn.apache.org/viewvc?rev=1102113&view=rev
[KARAF-539] - Document configfile xml tag of features


Modified: karaf/trunk/manual/src/main/webapp/users-guide/provisioning.conf
URL: http://svn.apache.org/viewvc/karaf/trunk/manual/src/main/webapp/users-guide/provisioning.conf?rev=1102113&r1=1102112&r2=1102113&view=diff
--- karaf/trunk/manual/src/main/webapp/users-guide/provisioning.conf (original)
+++ karaf/trunk/manual/src/main/webapp/users-guide/provisioning.conf Wed May 11 22:19:19 2011
@@ -212,6 +212,17 @@ class. Then we are passing in a beans ar
 For more informations about using the Configuration Admin service in Spring-DM, see the [Spring-DM
+h3. Configuration files
+*Available since Karaf 2.2*
+In certain cases it is needed not only to provide configurations for the configuration admin
service but to add additional configuration files e.g. a configuration file for jetty (jetty.xml).
It even might be help full to deploy a configuration file instead of a configuration for the
config admin service since. To achieve this the attribute {{finalname}} shows the final destination
of the {{configfile}}, while the value references the maven artifact to deploy.
+<configfile finalname="/etc/jetty.xml">mvn:org.apache.karaf/apache-karaf/${project.version}/xml/jettyconfig</configfile>
 h3. Feature resolver
 The resolver attribute on a feature can be set to force the use of a given resolver instead
of the default resolution process.  A resolver will be use to obtain the list of bundles to
actually install for a given feature.

View raw message