Closing chained I/O streams

Question

When chaining high-level I/O streams with low-level streams, without creating a reference to latter, are they getting closed automatically?
Let me clarify the situation.
That is a sample code from a book:
FileInputStream fis = new FileInputStream("file.txt");
BufferedInputStream bis = new BufferedInputStream(fis);
DataInputStream dis = new DataInputStream(bis);
* some code here
dis.close();
bis.close();
fis.close();As for me, I prefer cleaner solution, such as:
DataInputStream dis = new DataInputStream(new BufferedInputStream(new FileInputStream("file.txt")));But in this case, I can't close low level stream FileInputStream and BufferedInputStream, since I don't have any references to them.
Does the call to close() on BufferedInputStream object (bis.close()) automatically closes all lower-level streams?
Which snippet is usually considered a better approach to chaining streams?
Thank you.

Answer 1

AntShay wrote:
OK, and what is the preferred way of wrapping streams in real world?You mean individual variables vs. one longer statement that covers them all? I don't think it matters much, and I see both about equally. Some shops may have a standard that says you're not allowed to chain/nest in one statement, and my personal opinion is that it's better practice to have the individual statements, but I don't always follow it.
Also, does that mean, that manually closing FileInputStream and BufferedInputStream is somewhat unnecessary?If they're wrapped by another stream, then yes, closing them is unnecessary, and may actually be harmful, if you do it in the wrong order.