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

["Carsten Ziegeler (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FELIX-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved FELIX-3464.
-------------------------------------
    Resolution: Won't Fix

Resolving as won't fix - if this is still an issue with latest metatype/tooling, please reopen and update the issue

> 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
>            Priority: Major
>
> 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
(v8.20.10#820010)