You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "J.W. Janssen (JIRA)" <ji...@apache.org> on 2015/01/21 12:39:34 UTC

[jira] [Commented] (FELIX-3464) Raise exception when a Designate's OCDREF points to non-existing OCD

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

J.W. Janssen commented on FELIX-3464:
-------------------------------------

As far as I understand the spec, the OCD might not be included in a MetaType file, but provided externally. The use case I see in this is: a bundle registers a MetaType resource, for which an AutoConf file is used to define a (configuration) instance. In this situation, we cannot simply validate the {{ocdref}} using only its value...

> Raise exception when a Designate's OCDREF points to non-existing OCD
> --------------------------------------------------------------------
>
>                 Key: FELIX-3464
>                 URL: https://issues.apache.org/jira/browse/FELIX-3464
>             Project: Felix
>          Issue Type: Bug
>          Components: Metatype Service
>    Affects Versions: metatype-1.0.4
>            Reporter: Alexandre Castro Alves
>
> Currently, if a Designate's OCDREF references to a non-existing OCD, the MTI implementation simply ignores it.
> The result of this behavior is that the following code returns null both when (1) the designate ID is not defined in the meta-data, (2) the designate points to an invalid OCD:
> ObjectClassDefinition objClassDef = 
>             metaTypeInformation.getObjectClassDefinition(designateId, locale);
> It is my understanding from the spec that the latter situation should be treated as an exception.
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)