[
https://issues.apache.org/jira/browse/TIKA-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved TIKA-828.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.1
Assignee: Jukka Zitting
Thanks! I think that the latter option is actually better (see IO-192 for some
related discussion on this same problem), so in revision 1222880 I committed a
solution based on that idea along with your test case. Resolving as fixed.
PS. Unfortunately for API compatibility reasons we can't simply modify the
TaggedIOException class to match the one in Commons IO 2.0 after the IO-192
discussion. That, I think, would have been the ideal solution to this.
> TaggedIOException can be passed non Serializable objects
> --------------------------------------------------------
>
> Key: TIKA-828
> URL: https://issues.apache.org/jira/browse/TIKA-828
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Jerome Lacoste
> Assignee: Jukka Zitting
> Fix For: 1.1
>
> Attachments:
> 0003-TIKA-828-make-sure-the-exceptions-thrown-by-TaggedIn.patch
>
>
> TaggedIOException can contain tags. It's used to contain TaggedInputStream
> which isn't serializable.
> This can cause the ForkServer to fail when trying to report issues. See
> TIKA-827
> 2 solutions
> * make the tag transient
> * replace the InputStream instance in the tag by a serializable object
> specific to the input stream.
> I opt for the first one as I really don't think we need more complexity
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
