Am 02.09.15 um 07:03 schrieb Carsten Ziegeler:
> 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
Am 02.09.15 um 07:32 schrieb David Jencks:
> 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?
Yes, either html or json
> I think it would be sort of nice if
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
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
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
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?
