tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TIKA-139) Add a composite parser
Date Sun, 13 Apr 2008 16:59:05 GMT

    [ https://issues.apache.org/jira/browse/TIKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588405#action_12588405

Jukka Zitting commented on TIKA-139:

> How is this different from the AutoDetectParser

Separation of concerns. AutoDetectParser would both 1) auto-detect the content type, and 2)
use the type to select an underlying parser to which the parse call is delegated.

The CompositeParser as added in revision 647181 takes care of the latter concern. AutoDetectParser
now extends CompositeParser and just adds the auto-detection functionality.

> Add a composite parser
> ----------------------
>                 Key: TIKA-139
>                 URL: https://issues.apache.org/jira/browse/TIKA-139
>             Project: Tika
>          Issue Type: New Feature
>          Components: parser
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
> There should be a generic parser class that delegates parsing calls to underlying component
parsers based on the incoming document type metadata.

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

View raw message