felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Work started: (FELIX-1800) Bound configurations for which there exists no bundle cannot be edited
Date Fri, 23 Oct 2009 22:13:59 GMT

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

Work on FELIX-1800 started by Felix Meschberger.

> Bound configurations for which there exists no bundle cannot be edited
> ----------------------------------------------------------------------
>                 Key: FELIX-1800
>                 URL: https://issues.apache.org/jira/browse/FELIX-1800
>             Project: Felix
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: webconsole-2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
> Consider a configuration bound to a certain bundle [location]. If there is no bundle
installed with that bundle location, the configuration cannot be edited event though there
might be metatype information.
> The problem is that (1) metatype information is only retrieved for the bundle named by
the bundle location. It should probably be searched globally. (2) the configuration detail
information fails with a NullPointerException if there is no bundle with the bound location
> Another issue is, that existing configuration for which no metatype exists is not listed
in the drop-down, even though it can be rendered. The problem is an erratic (probably historic)
check for metatype information, which is not really required.
> Finally, the configuration properties are not displayed if there is no metatype information
because the client side rendering script does not attach the respect HTML elements to the
parent element.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message