[
https://issues.apache.org/jira/browse/LABS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630949#action_12630949
]
Thorsten Scherler commented on LABS-149:
----------------------------------------
Hi Javier,
I agree that the Parser interface needs to be changed.
http://markmail.org/message/vijohov4narssuv6
I think that what you refer to "Process interface" is already in Droids as
Handler. The ProcessOutgoingLinks should be Extractor since we do not want
their purpose only on links through naming (since they will extract new tasks
in general).
The processing should be something like
Parser (create SAX) -> Extracter (consume events and extract Tasks) -> Handler
(use original stream and/or SAX events from tika)
Can you come up with a patch?
TIA
> Extract the OutgoingLinks task from Parser interface
> ----------------------------------------------------
>
> Key: LABS-149
> URL: https://issues.apache.org/jira/browse/LABS-149
> Project: Labs
> Issue Type: Sub-task
> Components: Droids
> Reporter: Javier Puerto
>
> I'm working on the Tika integration with Droids but i found that the
> interface org.apache.droids.api.Parser force the task list to be in the
> parser phase. I think this is a problem, the process of the parsed data
> should be on other point after the extraction.
> The idea is to have an interface to extract the data (Parser) and a new
> interface to process the data (ex. Process).
> The change could be like this:
> Parser interface
> * Parse getParse(InputStream openStream);
> Process interface
> * void Process(InputStream openStream)
> ProcessOutgoingLinks interface (interface that extends from Process)
> * Task getOutgoingLinks(); << Previusly obtained from Process(inputStream)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
