Hi Lars,
Unfortunately <config/> doesn't overwrite the existing configuration, it
just introduces new one.
I raise a Jira to add the merge/overwrite capability on <config/>:
https://issues.apache.org/jira/browse/KARAF-1046
A possible workaround is to use <configfile/> which support
overwrite="true" (and which overwrite the existing configuration file).
Regards
JB
On 08/06/2012 01:59 PM, helander wrote:
Maybe I have misunderstood things. I am trying to provide configuration for
the http server using the following feature definition:
<feature name="httpserver-config" version="1.0.0">
<config name="org.ops4j.pax.web">
org.osgi.service.http.port = 8181
org.osgi.service.http.port.secure = 8443
org.osgi.service.http.enabled = true
org.osgi.service.http.secure.enabled = true
org.ops4j.pax.web.ssl.keystore = my.keystore
org.ops4j.pax.web.ssl.password = xyz
org.ops4j.pax.web.ssl.keypassword = abc
org.ops4j.pax.web.ssl.clientauthwanted = true
org.ops4j.pax.web.ssl.clientauthneeded = true
</config>
</feature>
When I install this feature nothing happens with the http-server
configuration and no information is put into the log.
Can someone provide any clarifications?
Thanks
Lars
--
View this message in context:
http://karaf.922171.n3.nabble.com/http-server-config-from-feature-tp4025430.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
