karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Assigned] (KARAF-2289) AJAX Error when editing some configurations in webconsole
Date Wed, 01 May 2013 08:50:16 GMT

     [ https://issues.apache.org/jira/browse/KARAF-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jean-Baptiste Onofré reassigned KARAF-2289:

    Assignee: Jean-Baptiste Onofré
> 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
> 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

View raw message