[
https://issues.apache.org/jira/browse/TIKA-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216451#comment-14216451
]
Chris A. Mattmann commented on TIKA-1445:
-----------------------------------------
Hey Guys, to be honest, the way I see that we solve the ServiceLoading problem
is somehow to move away from it. Relying on the JVM to implicitly decide which
parser to load based on ClassLoading is not scalable IMO. At worst, even
capturing an ordered preference file that isn't ServiceLoading is 1000x better
IMO than relying on the JVM and the classpath. We need somehow to bring this
logic into Tika (still thinking about how and will try to prototype something).
Further, as for the use case of 4-5 service files being common - I guess I'm
the outlier, b/c I've never ever created or used more than the default one?
> Figure out how to add Image metadata extraction to Tesseract parser
> -------------------------------------------------------------------
>
> Key: TIKA-1445
> URL: https://issues.apache.org/jira/browse/TIKA-1445
> Project: Tika
> Issue Type: Bug
> Components: parser
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 1.8
>
> Attachments: TIKA-1445.Mattmann.101214.patch.txt,
> TIKA-1445.Palsulich.102614.patch, TIKA-1445_tallison_20141027.patch.txt,
> TIKA-1445_tallison_v2_20141027.patch, TIKA-1445_tallison_v3_20141027.patch
>
>
> Now that Tesseract is the default image parser in Tika for many image types,
> consider how to add back in the metadata extraction capabilities by the other
> Image parsers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
