You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/02/12 06:04:57 UTC

[jira] Created: (OODT-138) Reference class prints stack trace when mime type repo cannot be found

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

        

[jira] Resolved: (OODT-138) Reference class prints stack trace when mime type repo cannot be found

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann resolved OODT-138.
------------------------------------

    Resolution: Fixed

- fixed in r1070027.

> 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
>              Labels: class, log, mime, output, pcs, reference, tika, type
>             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