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-23) Decouple Parser from ParserConfig
Date Fri, 21 Sep 2007 14:57:50 GMT

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

Jukka Zitting resolved TIKA-23.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.1-incubator

Patch committed in revision 578157.

> Decouple Parser from ParserConfig
> ---------------------------------
>
>                 Key: TIKA-23
>                 URL: https://issues.apache.org/jira/browse/TIKA-23
>             Project: Tika
>          Issue Type: Improvement
>          Components: general
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.1-incubator
>
>         Attachments: TIKA-23.patch
>
>
> Instead of starting from scratch with the new Parser interface design I proposed on the
mailing list, I'd like to work from the current codebase, iteratively refactoring it.
> The first problem I see with the current Parser design is the tight coupling with the
ParserConfig (and even LiusConfig) classes. Config objects are used both by ParserFactory
when  creating the parser instances and by the parser objects when parsing content. In fact
the parser classes even use the ParserConfig instances as containers of parsed content.
> This coupling makes it quite difficult to apply any structural changes to the parser
classes, so as a first step I'd like to propose a change that breaks this coupling.

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


Mime
View raw message