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] Resolved: (TIKA-26) Use Map<String, Content> instead of List<Content>
Date Tue, 25 Sep 2007 11:52:50 GMT

     [ https://issues.apache.org/jira/browse/TIKA-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jukka Zitting resolved TIKA-26.

    Resolution: Fixed

Fixed in revisions 579006, 579207, and 579208.

> Use Map<String, Content> instead of List<Content>
> -------------------------------------------------
>                 Key: TIKA-26
>                 URL: https://issues.apache.org/jira/browse/TIKA-26
>             Project: Tika
>          Issue Type: Improvement
>          Components: general
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.1-incubator
>         Attachments: TIKA-26.patch
> The current Parser classes take a List<Content> collection from ParserConfig, and
explicitly reformat that collection into an internal Map<String,Content> map keyed by
the Content names. I don't see any place where using a list of Content instances is better
than a Map keyed by the Content names, so I'd like to simplify things by creating the map
already in ParserConfig and using it directly ever since.

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

View raw message