[
https://issues.apache.org/jira/browse/KARAF-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072511#comment-13072511
]
Achim Nierbeck edited comment on KARAF-796 at 7/28/11 8:25 PM:
---------------------------------------------------------------
thanx for reporting. will be fixed in PaxWeb it's probably in the metatype.xml
corresponding pax web issue: http://team.ops4j.org/browse/PAXWEB-294
was (Author: achim_nierbeck):
thanx for reporting. will be fixed in PaxWeb it's probably in the
metatype.xml
> Editing Pax Web Configuration Via Karaf Console
> -----------------------------------------------
>
> Key: KARAF-796
> URL: https://issues.apache.org/jira/browse/KARAF-796
> Project: Karaf
> Issue Type: Bug
> Components: karaf-webconsole
> Affects Versions: 2.2.2
> Environment: Mac Snow Leopard 10.6.8, java 1.6.0_26, installed
> features: config/http/webconsole-base/webconsole/ssh/management (2.2.2),
> jetty(7.4.2.v20110526)
> Reporter: Gareth Collins
>
> If you try to change any PAX Web configuration via the karaf web console, it
> breaks PAX Web. After some research, I found at least one of the offending
> values created by Karaf webconsole:
> org.osgi.service.http.secure.enabled=B"true"
> PAX Web appears to expect this to be a string, not a boolean, so if I change
> this configuration value to this:
> org.osgi.service.http.secure.enabled="true"
> and I was able to get PAX Web working again.
> This may not be the only error in the file produced by Karaf (as I removed
> all the configuration items irrelevant to me currently).
> I only setup the minimum to get SSL working.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
