You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/04/28 14:25:32 UTC

[jira] Commented: (TIKA-298) CompositeParser.getParser() should use mimetype hierarchy when falling back

    [ https://issues.apache.org/jira/browse/TIKA-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861786#action_12861786 ] 

Jukka Zitting commented on TIKA-298:
------------------------------------

I implemented a simple version of this in revision 938966.

The fallback mechanism still doesn't support the full type hierarchy information in tika-mimetypes.xml, but already knows about base types and the hardcoded specialization rules in MediaType.isSpecializationOf().

> CompositeParser.getParser() should use mimetype hierarchy when falling back
> ---------------------------------------------------------------------------
>
>                 Key: TIKA-298
>                 URL: https://issues.apache.org/jira/browse/TIKA-298
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 0.4
>            Reporter: Ken Krugler
>
> CompositeParser.getParser() doesn't use supertypes when falling back - if it can't get a parser for the exact mimetype, then it goes
> straight to the fallback parser.
> So, for example, if the file mimetype is application/<whatever>+xml, and no parser exists for it, then you get the default "do nothing" parser versus the XML parser.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.