[
https://issues.apache.org/jira/browse/FELIX-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847370#action_12847370
]
Felix Meschberger commented on FELIX-1865:
------------------------------------------
Sorry for having had this laying around for much too long ....
I have to admit, that I do not completely understand the problem.
Here's what's going on in the web console:
* When a configuration (or ManagedService) is encountered the Web Console
scans all MetaTypeInformation
objects provided by the MetaTypeService for an ObjectClassDefinition with
the configuration's or service's
service.pid calling MetaTypeInformation.getObjectClassDefinition(String,
String)
* Once such an ObjectClassDefinition is found, it is used.
Now, the mapping of the Designate.pid attribute to the OCD.id attribute is
AFAICT the task of the MetaTypeService implementation. This service takes the
Object.ocdref attribute value and finds an OCD with a matching id attribute. If
no such OCD exists, the MetaTypeService (or rather the MetaTypeInformation)
should not resovle an ObjectClassDefinition for the Designate.
And, yes I may be missing something, particularly since you say that in 1.2.10
the configuration was properly rendered. Can you provide a Metatype descriptor
and a configuration exhibiting this proplem ? Thanks.
> 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.
