Y, that should be easy enough. Instead of the metadata list, we can store a
list of Metadata+Handler pairs, the current “getMetadata()” can be syntactic
sugar around the new getMetadataAndHandlers().
Please open a ticket and we can discuss there.
Thank you.
Best,
Tim
From: Andrea Asta [mailto:[email protected]]
Sent: Monday, September 21, 2015 8:00 AM
To: [email protected]
Subject: RecursiveParser returning ContentHandler
Hi,
I', trying to build a custom Conversion API using Tika: it just will add
"something before" and "something after" the Tika parsers.
In this scenario, I would like to build a mechanism to allow a custom object
being built starting from a parsing result. This can be done easily by working
with a custom ContentHandler "transformer", but how can I achieve this result
using a RecursiveParserWrapper? In this case I can only set a
ContentHandlerFactory and the parser will just call the toString method and set
it as a metadata, is it right? Can we imagine something to get the entire
ContentHandler object for each subfile instead of the result of the toString
method?
Thanks
Andrea
