[OODT-136] Lack of cataloged mime type causes recoverable exception in Reference core class

• 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
• Labels: mime oodt pcs reference tika type

Environment

while testing out pcs_trace

• Assignee: Chris A. Mattmann
• Reporter: Chris A. Mattmann
• Created: 10/Feb/11 14:49
• Updated: 10/Feb/11 15:44
• Resolved: 10/Feb/11 15:44

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.