Reference class prints stack trace when mime type repo cannot be found
----------------------------------------------------------------------
Key: OODT-138
URL: https://issues.apache.org/jira/browse/OODT-138
Project: OODT
Issue Type: Bug
Components: file manager
Affects Versions: 0.2
Environment: working on pcs
Reporter: Chris A. Mattmann
Assignee: Chris A. Mattmann
Priority: Critical
Fix For: 0.3
While testing out the PCS tools that I'm about to contributor in OODT-135, I
noticed that the Reference class barfs all over if the Tika mime-types.xml file
cannot be found, which often happens when e.g., filemgr.properties cannot be
found, but Reference is being used in some higher level downstream app (such as
PCS). Either way, the Reference class is such a low level core, class that it
shouldn't barf all over when it can't find its Mime type system. It should
gracefully fail (which it does, it defaults to the shipped Tika mime config --
the code just needs to be updated to not barf that message out everywhere).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
