You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/07/17 19:47:06 UTC

[jira] [Commented] (TIKA-1105) CompositeParser should use ParseContext when getting correct Parser

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

Hudson commented on TIKA-1105:
------------------------------

SUCCESS: Integrated in tika-trunk-jdk1.7 #98 (See [https://builds.apache.org/job/tika-trunk-jdk1.7/98/])
Fix for JIRA issue TIKA-1105, pass along ParseContext in CompositeParser. (tpalsulich: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1611405)
* /tika/trunk/tika-core/src/main/java/org/apache/tika/parser/CompositeParser.java


> CompositeParser should use ParseContext when getting correct Parser
> -------------------------------------------------------------------
>
>                 Key: TIKA-1105
>                 URL: https://issues.apache.org/jira/browse/TIKA-1105
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.3
>            Reporter: Luis Filipe Nassif
>            Assignee: Tyler Palsulich
>            Priority: Trivial
>         Attachments: TIKA-1105.palsulich.071614.patch
>
>
> CompositeParser uses getParser(metadata) into the parse() method. It creates a new ParseContext object and calls getParser(metadata, context).
> It should be better to directly call getParser(metadata, context) into the parse() method, using the supplied context, so it will take the context when  getting the supported types from loaded parsers.



--
This message was sent by Atlassian JIRA
(v6.2#6252)