[
https://issues.apache.org/jira/browse/TIKA-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512739#comment-16512739
]
Tim Allison edited comment on TIKA-2668 at 6/14/18 4:59 PM:
------------------------------------------------------------
There was some reworking of SAXException in jdk11. The exception used to == to
its cause, but with the reworking of SAXException, this is no longer true.
Given that as of jdk8 it looks like SAXException no longer has its own chaining
mechanism that would require {{initCause(original)}}; I think we can get rid of
it. It would be useful if I could find the source for SAXException in jdk5
and/or 6 to see what Jukka meant.
All tests pass in jdk8 and 10. The specific core test that I added now
passes with jdk 11.
e.g. from the original (in 2009/jdk6?):
{noformat}
initCause(original); // SAXException has it's own chaining mechanism!
{noformat}
was (Author: [email protected]):
There was some reworking of SAXException. The exception used to be == to its
cause, but with the reworking of SAXException, this is no longer true. Given
that as of jdk8, it looks like SAXException no longer has its own chaining
mechanism that would require {{initCause(original)}}. All tests pass in jdk8
and 10. The specific core test that I added now passes with jdk 11.
e.g. from the original (in 2009/jdk6?):
{noformat}
initCause(original); // SAXException has it's own chaining mechanism!
{noformat}
> Fix 'can't overwrite cause' exception in TaggedSAXException in Java 11-ea
> -------------------------------------------------------------------------
>
> Key: TIKA-2668
> URL: https://issues.apache.org/jira/browse/TIKA-2668
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> https://github.com/elastic/elasticsearch/issues/31305
> I can reproduce this with Java 11-ea in elastic's test harness and in a
> standalone unit test within tika-core.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
