Uploaded image for project: 'OODT'
  1. OODT
  2. OODT-136

Lack of cataloged mime type causes recoverable exception in Reference core class

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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.1-incubating, 0.2
    • Fix Version/s: 0.3
    • Component/s: file manager
    • Environment:

      while testing out pcs_trace

      Description

      I was testing out pcs_trace and noticed that the file manager has a pretty annoying bug in it that arose after OODT-58. As it turns out if there is a Product recorded in the o.a.oodt.cas.filemgr.catalog.Catalog interface implementation that does not have its mime type value recorded (either b/c mime type detection wasn't enabled at that point, or perhaps because it was an unrecognizable type, etc.) then the file manager will throw an exception when the Reference class tries to call its #setMimeType method. This is an easy fix – we just need to make sure that the provided mime type in #setMimeType(String) is not null or blank before passing it to Tika.

        Attachments

          Activity

            People

            • Assignee:
              chrismattmann Chris A. Mattmann
              Reporter:
              chrismattmann Chris A. Mattmann

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment