[jira] Resolved: (OODT-136) Lack of cataloged mime type causes recoverable exception in Reference core class

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

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

Chris A. Mattmann resolved OODT-136.
------------------------------------

    Resolution: Fixed

- fixed in r1069417.

> Lack of cataloged mime type causes recoverable exception in Reference core class
> --------------------------------------------------------------------------------
>
>                 Key: OODT-136
>                 URL: https://issues.apache.org/jira/browse/OODT-136
>             Project: OODT
>          Issue Type: Bug
>          Components: file manager
>    Affects Versions: 0.1-incubating, 0.2
>         Environment: while testing out pcs_trace
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>              Labels: mime, oodt, pcs, reference, tika, type
>             Fix For: 0.3
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira