NIO2 URI Runtime Exception

[John Freeman]

On page 458 of the study guide for OCP8 (Boyarsky, Selikoff) it is stated that the first Path statement below:

Path path1 = Paths.get(new URI("file://pandas/cuddly.png"));

Results in a runtime exception. However when I tried this on my own system (Windows 10), I did not get any runtime exception. Can someone help with this please?

import java.net.URI;
import java.net.URISyntaxException;
import java.nio.file.Path;
import java.nio.file.Paths;

public class NIO2 {

	public static void main(String[] args) {
		// TODO Auto-generated method stub
		try {
			Path path1 = Paths.get(new URI("file://pandas/cuddly.png"));
		} catch (Exception e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}
	}

}

[Scott Selikoff]

See the paragraph after this example: "The first example actually throws an exception at runtime, as URIs must reference absolute paths at runtime" and see the feature on the previous page titled "Absolute vs a Relative is file system dependent".

In other words, it is file system dependent to some degree whether the runtime exception will be thrown.

[John Freeman]

Scott Selikoff wrote:See the paragraph after this example: "The first example actually throws an exception at runtime, as URIs must reference absolute paths at runtime" and see the feature on the previous page titled "Absolute vs a Relative is file system dependent".

In other words, it is file system dependent to some degree whether the runtime exception will be thrown.

Thanks for the reply Scott. In the example I posted above, I added a check :

System.out.println(path1.isAbsolute());

and this returned true, so this explained why this resulted in no runtime exception.

Then I tried this:

Path path4 = Paths.get(new URI("pandas/cuddly.png"));

and this time I got a runtime exception. So it seems like the schema "file://" made the difference in making it an absolute path on my system, therefore I didn't need the 3 slashes as in path3 on page 458.