You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Achim Nierbeck (JIRA)" <ji...@apache.org> on 2010/12/13 21:44:17 UTC

[jira] Commented: (FELIX-1865) Metatype resolving mechanism does not seem to work correctly

    [ https://issues.apache.org/jira/browse/FELIX-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971028#action_12971028 ] 

Achim Nierbeck commented on FELIX-1865:
---------------------------------------

Just stumbled over this, but It looks to me I found this issue also with 3.1.2

Using a metatype like the following: 

<metatype:MetaData xmlns:metatype="http://www.osgi.org/xmlns/metatype/v1.0.0">
	<OCD id="a.b.c.d-service" />

...

	<Designate pid="a.b.c.d">
		<Object ocdref="a.b.c.d-service" />
	</Designate>
</metatype:MetaData>

Where the pid is a.b.c.d and the reference is the pid with an appended -service. 

Now what happens is that there is a entry for a.b.c.d and another one for a.b.c.d-service (while debugging this seemed to be added as managed factory?)

Unless I'm wrong with my interpretation but I think this shouldn't happen.

> Metatype resolving mechanism does not seem to work correctly
> ------------------------------------------------------------
>
>                 Key: FELIX-1865
>                 URL: https://issues.apache.org/jira/browse/FELIX-1865
>             Project: Felix
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: webconsole-2.0.2
>         Environment: equinox 3.5.1 (release; cm, metatype from the same release)
>            Reporter: Dieter Wimberger
>
> The implementation of the metatype mechanism in the web-console 2.0.2  causes configurations to be listed with the Designate pid and the Object ocdref. 
> i.e.
> <Designate pid="com.acme.addressbook">
>    <Object ocdref="2.5.6.6"/>
> </Designate> 
> Would list "com.acme.addressbook" and "2.5.6.6" where the latter is actually broken and won't load the corresponding form.
> This problem does not occur with the identical installation and a web-console 1.2.10 release bundle.

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