[
https://issues.apache.org/jira/browse/TIKA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith R. Bennett updated TIKA-34:
---------------------------------
Attachment: tika-34.patch
The attached patch:
1) Adds a method to Utils called getDefaultConfig() that returns a newly
created TikaConfig instance using the tika-config.xml file. (I guessed that
Utils was a logical place to put it -- feel free to move it.) If/when
TikaConfig is 100% immutable, we can have it return a shared instance if we
want.
2) Moved tika-config.xml to org.apache.tika. This is to reduce the risk that a
file of that name will exist elsewhere in the classpath. (Again, feel free to
not move it if you like.)
Ideally, it would be nice to provide parse methods that did not require
specifying a configuration, and using a default; this is a step in that
direction, but also is useful on its own.
> Provide a method that will return a default configuration (TikaConfig).
> -----------------------------------------------------------------------
>
> Key: TIKA-34
> URL: https://issues.apache.org/jira/browse/TIKA-34
> Project: Tika
> Issue Type: New Feature
> Components: general
> Affects Versions: 0.1-incubator
> Reporter: Keith R. Bennett
> Priority: Minor
> Fix For: 0.1-incubator
>
> Attachments: tika-34.patch
>
>
> Although a default configuration is available, one must explicitly specify
> its location and open a stream from that location.
> It would be helpful to have a method that returns the default configuration,
> parsed and ready to use, so that the users can be insulated from the
> implementation of how and where we store it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
