You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Riccardo Tomasi (JIRA)" <ji...@apache.org> on 2013/05/17 18:53:16 UTC
[jira] [Commented] (KARAF-2289) AJAX Error when editing some
configurations in webconsole
[ https://issues.apache.org/jira/browse/KARAF-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660849#comment-13660849 ]
Riccardo Tomasi commented on KARAF-2289:
----------------------------------------
I confirm this bug under Xubuntu Linux 12.02 x86
> AJAX Error when editing some configurations in webconsole
> ---------------------------------------------------------
>
> Key: KARAF-2289
> URL: https://issues.apache.org/jira/browse/KARAF-2289
> Project: Karaf
> Issue Type: Bug
> Components: webconsole
> Affects Versions: 2.3.1
> Environment: Windows 7 Pro x64
> Reporter: Jeff Clark
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.3.2
>
>
> I was working through Christian Schneider's Karaf tutorial #3 (http://www.liquid-reality.de/display/liquid/2011/09/26/Karaf+Tutorial+Part+3+-+Improving+configuration+editing+using+the+OSGI+Metatype+Service+and+the+Felix+Webconsole). After presenting my findings to Christian, he believes this is a bug in the webconsole for this version of Karaf, and asked me if I could open an issue here.
> The problem is that after building his ConfigAdmin project & installing in Karaf, if you attempt to edit that project's configuration (ConfigApp.cfg) file through the webconsole, the following error is raised:
> AJAX Error
> The request failed:
> {"PID":"ConfigAdmin"
> If I uninstall the configapp & configapp-blueprint features, I can then edit the remaining ConfigApp.cfg file through the webconsole, receiving the message that the form was automatically generated because no property descriptors are available (which makes sense because I uninstalled the associated features).
> His tutorial references Karaf 2.2.4 which did not have this problem, and he has tested in 3.0.0.RC1 without seeing this problem. 2.3.1 however seems to have this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira