[jira] Created: (TIKA-133) TeeContentHandler constructor should use varargs

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (TIKA-133) TeeContentHandler constructor should use varargs

JIRA jira@apache.org
TeeContentHandler constructor should use varargs
------------------------------------------------

                 Key: TIKA-133
                 URL: https://issues.apache.org/jira/browse/TIKA-133
             Project: Tika
          Issue Type: Improvement
            Reporter: Jukka Zitting
            Assignee: Jukka Zitting
            Priority: Minor


Currently the TeeContentHandler only branches the incoming SAX event stream to two underlying handlers. There is no reason it couldn't handle any number of underlying handlers, and the most straightforward way to do that is to allow varargs in the constructor:

    public TeeContentHandler(ContentHandler... handlers)

Doing this introduces a minor backwards incompatibility with the 0.1 release, but I think it's worth it especially since we explicitly made no API stability promises in 0.1.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (TIKA-133) TeeContentHandler constructor should use varargs

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/TIKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved TIKA-133.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.2-incubating

Done in revision 641374.

> TeeContentHandler constructor should use varargs
> ------------------------------------------------
>
>                 Key: TIKA-133
>                 URL: https://issues.apache.org/jira/browse/TIKA-133
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.2-incubating
>
>
> Currently the TeeContentHandler only branches the incoming SAX event stream to two underlying handlers. There is no reason it couldn't handle any number of underlying handlers, and the most straightforward way to do that is to allow varargs in the constructor:
>     public TeeContentHandler(ContentHandler... handlers)
> Doing this introduces a minor backwards incompatibility with the 0.1 release, but I think it's worth it especially since we explicitly made no API stability promises in 0.1.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.