This means that every time a parse methods that uses a default configuration
is used, the default configuration's XML will be reparsed. This may not be
a big deal for apps that only occasionally do this, but for an app whose
mission is to parse documents, it seems kind of wasteful, especially when it
can be remedied with a small number of simple lines of code. Certainly I
can get the default configuration once, hold onto it, and then call the
parse methods that take it, but it seems odd to me that I would have to do
that. I realize it's a minor issue, though.
- Keith
Bertrand Delacretaz wrote:
>
> On 9/25/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
>
>> ...How about something like this:
>>
>> public static TikaConfig getDefaultConfig()
>> throws IOException, JDOMException {
>> return new TikaConfig(
>> TikaConfig.class.getResourceAsStream("tika-config.xml"));
>> }...
>
> Agreed, this is good enough.
>
> -Bertrand
>
>
--
View this message in context:
http://www.nabble.com/Providing-a-Default-Tika-Configuration-tf4510478.html#a12880793
Sent from the Apache Tika - Development mailing list archive at Nabble.com.
