[ 
https://issues.apache.org/jira/browse/TIKA-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427563#comment-16427563
 ] 

ASF GitHub Bot commented on TIKA-2623:
--------------------------------------

OhadR opened a new pull request #233: fix TIKA-2623: "get embedded resources in 
doc files" (by OhadR)
URL: https://github.com/apache/tika/pull/233
 
 
   i have refactored `FileEmbeddedDocumentExtractor`: moved it from tika-cli to 
tika-parsers, so applications that are dependent on tika-parser, but not on 
tika-app, can use it.
   
   maybe tika-core could be a better place to put this file (like 
'ParsingEnbeddedDocumentExtractor'), but then the pom.xml needs to be changed: 
need to add dependencies of apache-common-io, poi, etc. and we do not wanna do 
that, because we do not want to add dependencies to tika-core.
   
   
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> get embedded resources in doc files
> -----------------------------------
>
>                 Key: TIKA-2623
>                 URL: https://issues.apache.org/jira/browse/TIKA-2623
>             Project: Tika
>          Issue Type: Improvement
>          Components: cli, core, parser
>            Reporter: Ohad R
>            Priority: Trivial
>
> according to 
> [https://stackoverflow.com/questions/20172465/get-embedded-resourses-in-doc-files-using-apache-tika,]
>  it is possible to recursively parse a document and save its sub-items (e.g. 
> images) in a folder thanks to FileEmbeddedDocumentExtractor. However, the 
> scope of the above class is only in the TikaCLI.
> I think it should be visible to the applications that uses Tika (not only to 
> the CLI)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to