Hi, Petr.
Submitter complains about IOException itself, not about incorrect stack
trace.
On 5/22/14 1:39 PM, Anthony Petrov wrote:
Looks fine.
--
best regards,
Anthony
On 5/21/2014 4:27 PM, Petr Pchelko wrote:
Hello, AWT Team.
Please review the fox for the issue:
https://bugs.openjdk.java.net/browse/JDK-8043513
The fix is available at:
http://cr.openjdk.java.net/~pchelko/9/8043513/webrev/
The problem:
When we fetch all contents from the clipboard we catch IOException
and store it for later.
In case we would then need the data which caused the exception the
cached exception would be rethrown.
But the stack trace shows where the exception was created, not
thrown. Wrapping it helps to
eliminate the misunderstanding.
With best regards. Petr.
--
Best regards, Sergey.
