[
https://issues.apache.org/jira/browse/TIKA-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653319#comment-14653319
]
Nick Burch commented on TIKA-1680:
----------------------------------
Why do we need to kill service loading? For many users in simpler setups, it
just works, and lets them easily add in new parsers with very little effort!
Anyone who doesn't want service loading can just skip Default{Parser,Detector}
from their Tika Config, and it isn't used
> Add configuration layer to configure, Parsers default configurable properties.
> ------------------------------------------------------------------------------
>
> Key: TIKA-1680
> URL: https://issues.apache.org/jira/browse/TIKA-1680
> Project: Tika
> Issue Type: Improvement
> Components: config
> Reporter: Mario Costa
> Priority: Minor
>
> In several conditions, we want to change the default tika configuration, for
> some specific parsers, to change the behaviour of libraries/components
> wrapped in the parsers.
> Currently, the ParseContext class allows, for means of passing this default
> configuration.
> Add means, to load from a configuration database/files default configuration
> to override, currently hard coded, defaults.
> E.g. #TIKA-640, there are no means to change the defaults, by means of
> configuration files, with out having to change, tika source.
> - Sugestion
> - Add a ParserConfigurationFactory, to delegate configuration loading, to a
> database/property based file etc.
> - Allow for configuration factory instance to be configured via file, like
> tika-config.xml for Parsers.
> interface ParserConfigurationFactory {
> /**
> * Create or fille the given ParseContext with the default configuration for
> the parser class...
> */
> <P extends Parser> ParseContext getDefaultConfig(Class<P> class,
> ParseContext ctx);
> }
> Replace when creating a ParseContext, by
> ParseContext ctx =
> ParserConfigurationFactorySingleton.getSingleton().getDefaultConfig(...) ...
> Filling the configuration, given a set of properties, could be done via a
> class <ParserName>ConfigBuilder that know how to build and set the
> configuration properties in specific objects (such as MimeConfig), related to
> 3rd party external libraries ...
> Best regards,
> mc
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
