You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2014/12/29 15:30:13 UTC
[jira] [Updated] (FELIX-3366) The Configuration Webconsole Plugin
seems to ignore the ocd ref element
[ https://issues.apache.org/jira/browse/FELIX-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated FELIX-3366:
------------------------------------
Summary: The Configuration Webconsole Plugin seems to ignore the ocd ref element (was: The Konfiguration Webconsole Plugin seems to ignore the ocd ref element)
> The Configuration Webconsole Plugin seems to ignore the ocd ref element
> -----------------------------------------------------------------------
>
> Key: FELIX-3366
> URL: https://issues.apache.org/jira/browse/FELIX-3366
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Environment: Equinox container with apache felix webadmin, http und metatype bundle
> Reporter: Christoph Läubrich
> Priority: Minor
>
> If there is a desiginator like this:
> <OCD id="test.config.pid" .... >
> <Designate pid="test.config.pid">
> <Object ocdref="test.config.pid" />
> </Designate>
> everythiong works fine.
> Using something different ad the OCD Id than the pid makes the webconsole plugin thing there is no OCD at all (it just provides a textfield where you can enter the properties by name):
> <OCD id="ocd1" .... >
> <Designate pid="test.config.pid">
> <Object ocdref="ocd1" />
> </Designate>
> maybe I get something wrong but I can't see from the spec that the pid must equal the ocd id (in fact the examples does alwys use a different name) the metatype service itself has not any problem with both notations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)