You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Keith R. Bennett (JIRA)" <ji...@apache.org> on 2007/09/27 00:31:50 UTC
[jira] Created: (TIKA-34) Provide a method that will return a
default configuration (TikaConfig).
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
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.
[jira] Updated: (TIKA-34) Provide a method that will return a
default configuration (TikaConfig).
Posted by "Keith R. Bennett (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (TIKA-34) Provide a method that will return a
default configuration (TikaConfig).
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann closed TIKA-34.
---------------------------------
Committed with minor modifications in r581280. Thanks, Keith!
> 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
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.1-incubator
>
> Attachments: tika-34-20071001.patch, 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.
[jira] Resolved: (TIKA-34) Provide a method that will return a
default configuration (TikaConfig).
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann resolved TIKA-34.
-----------------------------------
Resolution: Fixed
- adapted patch slightly:
1. didn't move tika-config.xml to src/resources/org/apache/tika (just changed it to a maven copy task as part of the build)
2. moved getDefaultConfig to TikaConfig (to me it's really a part of TikaConfig, rather than a generic utility) rather than Utils
3. fixed formatting in TestParsers (seemed kind of funky?)
> 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
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.1-incubator
>
> Attachments: tika-34-20071001.patch, 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.
[jira] Assigned: (TIKA-34) Provide a method that will return a
default configuration (TikaConfig).
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann reassigned TIKA-34:
-------------------------------------
Assignee: Chris A. Mattmann
> 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
> Assignee: Chris A. Mattmann
> 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.
[jira] Updated: (TIKA-34) Provide a method that will return a
default configuration (TikaConfig).
Posted by "Keith R. Bennett (JIRA)" <ji...@apache.org>.
[ 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-20071001.patch
The attached patch adds a getDefaultConfig() method to Utils, plus some supporting methods and test code.
The tika-config.xml file is moved from src/test/resources src/test/resources/org/apache/tika.
While I was there, I fixed a few lines in TestParsers whose lengths were > 80.
(I am giving the new patch a different name so the old patch remains available in case that should be necessary.)
> 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
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.1-incubator
>
> Attachments: tika-34-20071001.patch, 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.