On Tue, 13 Mar 2012, Jon Gorrono wrote:
The tika-app jar properly identifies the misnamed file so it's either a classpath or a implementation issue
You'll need to have the Tika Parsers jar (and associated dependencies) for it to work properly. We do have unit tests for this, and as long as the parser jar + dependencies are there, then the appropriate detector will fire. It may be worth making sure you use a recent nightly build, or waiting for Tika 1.1 (hopefully due soon) though, as I seem to recall we had to fix an ordering problem at some point
Also ContainerAwareDetector does not seem to exist in 1.0 ... this leads me to think that that part was abstracted for ease of use and the docs are now outdated(?)
Which docs were you looking at? ContainerAwareDetector has gone, yes, it's now handled by the same service loading mechanism that parsers use
But should I then be wrapping the inputstream in a TikaInputStream?
If you have a File, then I'd suggest you use a TikaInputStream
I also tried the detection after creating a spingbean for the Tika class in the hope that it might wake up a hidden 'inner-self' :)
Not sure if it'll help or not, but you could look at Alfresco for an example (though a large one!) of using spring beans with Tika for detection
Nick
