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

ASF GitHub Bot commented on ANY23-396:
--------------------------------------

Github user HansBrende commented on the issue:

    https://github.com/apache/any23/pull/122
  
    As per part 4 of my last comment, in my most recent commit I've allowed 
`FormatWriterFactory` and `DelegatingWriterFactory` to extend the same 
(package-private) base interface specifying a single generic method:
    
    ```java
    interface BaseWriterFactory<Output> extends WriterFactory {
        TripleHandler getTripleWriter(Output o);
    }
    ```
    
    I could have added this method directly to `WriterFactory` (with a default 
implementation of throwing `UnsupportedOperationException`), but since all 
instances of this interface *must* be instances of either `FormatWriterFactory` 
or `DelegatingWriterFactory` (since the interface is package-private), and all 
interaction with this method will be done by casting to one of these two 
interfaces, adding generic arguments to `WriterFactory` itself would have only 
added unnecessary verbosity (e.g., always having to specify `WriterFactory<?>` 
instead of `WriterFactory` to avoid rawtypes warnings).
    
    @lewismc any comments?


> Add ability to run extractors in flow
> -------------------------------------
>
>                 Key: ANY23-396
>                 URL: https://issues.apache.org/jira/browse/ANY23-396
>             Project: Apache Any23
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.2
>            Reporter: Jacek Grzebyta
>            Assignee: Jacek Grzebyta
>            Priority: Minor
>
> Currently extractors do not work in flows. I.E. Next extractor has no any 
> access to triples made by previous one.
> It would be useful if an extractor has possibility to modify triples created 
> by another extractor.
>  



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

Reply via email to