I haven’t looked at the web console. There’s already the ScriInfo service which is used by the gogo and non-gobo console commands, but I guess you need html for the web console? I think it would be sort of nice if all the descriptive tools had related-looking outputs. Maybe a visitor pattern might be possible?
BTW I’m not entirely happy with how the ScrInfo output looks… I’m thinking the summary view ought to show the one-line descriptions followed by 1-line configurations. There’s also a bug in the long view…. hopefully I can fix these soon. thanks david jencks > On Sep 2, 2015, at 1:03 AM, Carsten Ziegeler <[email protected]> wrote: > > Am 01.09.15 um 16:33 schrieb Carsten Ziegeler: >> Am 01.09.15 um 16:30 schrieb Bertrand Delacretaz: >>> Hi, >>> >>> Using the latest org.apache.felix.webconsole 4.2.10 in Sling, if I >>> deactivate a component at /system/console/components it disappears >>> from the list (and from the underlying json data). >>> >>> Unless I'm missing something, this makes it impossible to reactivate >>> the component. >>> >>> Is this a known issue? >>> >> I assume that's the DS webconsole plugin, not the webconsole itself >> > Strange, somehow my second paragraph did not make it into the email: > The R6 Declarative Service specification has a clarified component model > and distinguishes between component descriptions and configurations. > While the console displays the configurations, enabling and disabling is > only based on the descriptions. Therefore disabling means the > configurations are removed and nothing is displayed. I think we have to > change the webconsole plugin. > > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected]
