Hi, all. Whenever we talk about the TikaConfig object, we talk of configuring it using XML.
I'd like to suggest that we provide an API as well. In general, it would be easier to use in many cases. Also: * The default configuration may be suitable most of the time, but if a user wants to change only 1 or 2 options, having to create a new XML file is overkill. It would be much easier to load the default and call a method or two to deviate from the default. * The desired options may not be known until runtime. Having to build a Document in memory, or write an XML file, seems like more work than should be necessary. * One might want to keep a single instance in memory and modify it over the life of the program as necessary. * In general, I think one shouldn't need to know about an external representation of an object (TikaConfig's XML representation in this case) if working with the object directly is simpler. What do you think? Should I create a JIRA issue for this? - Keith -- View this message in context: http://www.nabble.com/XML-as-Only-Route-to-TikaConfig-tf4616942.html#a13185694 Sent from the Apache Tika - Development mailing list archive at Nabble.com.
