[
https://issues.apache.org/jira/browse/FELIX-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-2879:
-------------------------------------
Component/s: (was: Metatype Service)
Web Console
Affects Version/s: webconsole-3.1.8
Fix Version/s: webconsole-3.1.10
Assignee: Felix Meschberger
Thanks for reporting.
This is in fact a bug in how the Web Console configuration support treats the
object classes: It assumes the ObjectClass ID is in fact the Service PID (or
factory PID), which of course is wrong (it just happens so when using the Maven
SCR Plugin).
> Metatype Service confuses the id of the OCD with the Designate.pid/factoryPid.
> ------------------------------------------------------------------------------
>
> Key: FELIX-2879
> URL: https://issues.apache.org/jira/browse/FELIX-2879
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-3.1.8
> Reporter: Peter Kriens
> Assignee: Felix Meschberger
> Priority: Critical
> Fix For: webconsole-3.1.10
>
>
> I've been adding a facility to bnd to use metatypes with components. I
> noticed that the Designate pid or factoryPid was not used as the pid but
> instead the the OCD id was used. As far as I can read the spec this is wrong,
> what would be the purpose of the Designate element?
> The following
> <metatype:MetaData xmlns:metatype='http://www.osgi.org/xmlns/metatype/v1.1.0'>
> <OCD name='Basic component config' id='ocd'>
> <AD name='Message' id='message' cardinality='0' required='false'
> type='String'/>
> </OCD>
> <Designate pid='pid'>
> <Object ocdref='ocd'/>
> </Designate>
> </metatype:MetaData>
> Will be see as a pid of "ocd" and strangely enough there will be no
> interpretation of the metatype. Making pid and ocd id equal makes it work.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
