Uploaded image for project: 'Felix'
  1. Felix
  2. FELIX-3464

Raise exception when a Designate's OCDREF points to non-existing OCD

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • metatype-1.0.4
    • None
    • Metatype Service
    • None

    Description

      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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            adcalves Alexandre Castro Alves
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment