You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/07/30 14:12:34 UTC
[jira] [Commented] (FELIX-3614) In latest webconsole no property
descriptors are available
[ https://issues.apache.org/jira/browse/FELIX-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424811#comment-13424811 ]
Felix Meschberger commented on FELIX-3614:
------------------------------------------
Thanks for reporting the issue.
This is probably caused by inappropriate migration of static imports to dynamic imports.
In this particular case, the package is embedded by intent to be able to render the configuration even in the absence of a MetaTypeService.
I see multiple options:
* Separate Metatype support from the rest of the configuration support and only use metatype if available
* export and re-import the metatype API and thus be friendly to the environment using whatever is provided
* embed the API and import optionally (but statically). This is not as friendly as the second option because it might cause type mismatches between a future provider and the web console.
As a workaround, I would think that refrshing the Web Console bundle might also do the trick.
> In latest webconsole no property descriptors are available
> ----------------------------------------------------------
>
> Key: FELIX-3614
> URL: https://issues.apache.org/jira/browse/FELIX-3614
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-4.0.0
> Reporter: Jonathan Anstey
> Attachments: webconsole_metatype.patch
>
>
> I noticed that in the latest webconsole (version 4.0.0) all items in the config tab don't have the custom property descriptor shown - just default ones with this message:
> "This form is automatically generated from existing properties because no property descriptors are available for this configuration. This may be cause by the absence of the OSGi Metatype Service or the absence of a MetaType descriptor for this configuration."
> This problem didn't occur in the previous release of 3.1.8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira