Modernjava.io Website Review

Reading and writing from files or streams in older versions of Ja*a were error prone and verbose, but slowly, over time, the situation has improved considerably, first with try-with-resources, and then with NIO 2, and with some nice additions over the last year. So here’s a To show you how bad IO used to be in Ja*a 5, check out this example:         while ((i = fin.read()) != -1) {             System.out.println((char) i);     } catch (IOException e) {         throw new UncheckedIOException(Could not load file, e);     } finally {         if (fin != null) {             try {                          fin.close(); } catch (FileNotFoundException e) {     throw new UncheckedIOException(Could not find file, e);     throw new UncheckedIOException(Could not load file, e); } These two examples aren’t completely identical, because writing the first example to replicate the second requires considerably more lines of clean up code, which almost certainly won’t be correct. The error handling for all these examples will involve the same exceptions, namely IOException, which as a checked exception, you’ll need to handle. You’ll also get NoSuchFileExpection, which is a subclas* of IOException, so you can choose to handle that situation separately, or just handle IOException. In these examples, I’ll show handling the IOException by wrapping the exception in an UncheckedIOException. You should do the appropriate error handling for your situation. It is very important that you remember to specify a charset in these situations, because the single parameter constructor uses the system default charset, which may be different from one JVM to another. UTF-8 is a decent default. The methods in ja*a.nio.files.Files use UTF-8 as the default, rather than the system default encoding, so you do not need to specify the charset here. If you need an alternative charset, there is an overloaded version that takes a Charset object.