[
https://issues.apache.org/jira/browse/TIKA-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259301#comment-17259301
]
Peter Kronenberg commented on TIKA-3263:
----------------------------------------
Yes, throwing an exception in the first place seemed a bit much . But at least
if it was public, I could handle it. Metadata wouldn't be a bad idea, although
then the user would have to know to check that. If you have a huge file, you
don't want to just blow up and throw away all the work that's been done so far.
(by the way, did my images come through on this issue? I got errors when I
uploaded them, but I was able to see them)
> WriteLimitReachedException is not public
> ----------------------------------------
>
> Key: TIKA-3263
> URL: https://issues.apache.org/jira/browse/TIKA-3263
> Project: Tika
> Issue Type: Improvement
> Environment: Windows 10
> Reporter: Peter Kronenberg
> Priority: Minor
>
> I got a WriteLimitReachedException because my file was too big. The message
> tells me that the text up the limit is still available. However, it’s tricky
> to get that text and at the same time, respond appropriately to
> SAXExceptions. Originally, my method was catching SAXEXceptions and assume
> there was an error.
> What I really want to do it to be able to catch WriteLimitReachedException,
> but still throw other SAXExceptions, which would indicate that something else
> went wrong. But since WriteLimitReachedException is private, I can’t do that.
>
> Here’s what my code originally looked like:
> !Code1.png!
> But this didn’t work, because if I get a WriteLimitReachedException, it
> doesn’t tell me what data that it got
>
> Given this new knowledge, here’s what I want to do, but I can't, because
> WriteLimitReachedException is private. There's no reason for it to be
> private.
>
> !Code2.png!
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
