
- •Contents at a Glance
- •Contents
- •About the Authors
- •About the Technical Reviewer
- •Acknowledgments
- •Introduction
- •Oracle Java Certifications: Overview
- •FAQ 1. What are the different levels of Oracle Java certification exams?
- •FAQ 4. Is OCPJP 7 prerequisite for other Oracle certification exams?
- •FAQ 5. Should I take the OCPJP 7 or OCPJP 6 exam?
- •The OCPJP 7 Exam
- •FAQ 7. How many questions are there in the OCPJP 7 exam?
- •FAQ 8. What is the duration of the OCPJP 7 exam?
- •FAQ 9. What is the cost of the OCPJP 7 exam?
- •FAQ 10. What are the passing scores for the OCPJP 7 exam?
- •FAQ 11. What kinds of questions are asked in the OCPJP 7 exam?
- •FAQ 12. What does the OCPJP 7 exam test for?
- •FAQ 13. I’ve been a Java programmer for last five years. Do I have to prepare for the OCPJP 7 exam?
- •FAQ 14. How do I prepare for the OCPJP 7 exam?
- •FAQ 15. How do I know when I’m ready to take the OCPJP 7 exam?
- •Taking the OCPJP 7 Exam
- •FAQ 16. What are my options to register for the exam?
- •FAQ 17. How do I register for the exam, schedule a day and time for taking the exam, and appear for the exam?
- •The OCPJP 7 Exam: Pretest
- •Answers with Explanations
- •Post-Pretest Evaluation
- •Essentials of OOP
- •FunPaint Application: An Example
- •Foundations of OOP
- •Abstraction
- •Encapsulation
- •Inheritance
- •Polymorphism
- •Class Fundamentals
- •Object Creation
- •Constructors
- •Access Modifiers
- •Public Access Modifier
- •Private Access Modifier
- •Protected and Default Access Modifier
- •Overloading
- •Method Overloading
- •Constructor Overloading
- •Overload resolution
- •Points to Remember
- •Inheritance
- •Runtime Polymorphism
- •An Example
- •Overriding Issues
- •Overriding: Deeper Dive
- •Invoking Superclass Methods
- •Type Conversions
- •Upcasts and Downcasts
- •Casting Between Inconvertible Types
- •Using “instanceof” for Safe Downcasts
- •Java Packages
- •Working with Packages
- •Static Import
- •Summary
- •Abstract Classes
- •Points to Remember
- •Using the “final” Keyword
- •Final Classes
- •Final Methods and Variables
- •Points to Remember
- •Using the “static” Keyword
- •Static Block
- •Points to Remember
- •Flavors of Nested Classes
- •Static Nested Classes (or Interfaces)
- •Points to Remember
- •Inner Classes
- •Points to Remember
- •Local Inner Classes
- •Points to Remember
- •Anonymous Inner Classes
- •Points to Remember
- •Enum Data Types
- •Points to Remember
- •Summary
- •Interfaces
- •Declaring and Using Interfaces
- •Points to Remember
- •Abstract Classes vs. Interfaces
- •Choosing Between an Abstract Class and an Interface
- •Object Composition
- •Composition vs. Inheritance
- •Points to Remember
- •Design Patterns
- •The Singleton Design Pattern
- •Ensuring That Your Singleton Is Indeed a Singleton
- •The Factory Design Pattern
- •Differences Between Factory and Abstract Factory Design Patterns
- •The Data Access Object (DAO) Design Pattern
- •Points to Remember
- •Summary
- •Generics
- •Using Object Type and Type Safety
- •Using the Object Class vs. Generics
- •Container Implementation Using the Object Class
- •Container Implementation Using Generics
- •Creating Generic Classes
- •Diamond Syntax
- •Interoperability of Raw Types and Generic Types
- •Generic Methods
- •Generics and Subtyping
- •Wildcard Parameters
- •Limitations of Wildcards
- •Bounded Wildcards
- •Wildcards in the Collections Class
- •Points to Remember
- •The Collections Framework
- •Why Reusable Classes?
- •Basic Components of the Collections Framework
- •Abstract Classes and Interfaces
- •Concrete Classes
- •List Classes
- •ArrayList Class
- •The ListIterator Interface
- •The LinkedList Class
- •The Set Interface
- •The HashSet Class
- •The TreeSet Class
- •The Map Interface
- •The HashMap Class
- •Overriding the hashCode() Method
- •The NavigableMap Interface
- •The Queue Interface
- •The Deque Interface
- •Comparable and Comparator Interfaces
- •Algorithms (Collections Class)
- •The Arrays Class
- •Methods in the Arrays Class
- •Array as a List
- •Points to Remember
- •Summary
- •Generics
- •Collections Framework
- •Processing Strings
- •String Searching
- •The IndexOf() Method
- •The regionMatches() Method
- •String Parsing
- •String Conversions
- •The Split() Method
- •Regular Expressions
- •Understanding regex Symbols
- •Regex Support in Java
- •Searching and Parsing with regex
- •Replacing Strings with regex
- •String Formatting
- •Format Specifiers
- •Points to Remember
- •Summary
- •Reading and Writing from Console
- •Understanding the Console Class
- •Formatted I/O with the Console Class
- •Special Character Handling in the Console Class
- •Using Streams to Read and Write Files
- •Character Streams and Byte Streams
- •Character Streams
- •Reading Text Files
- •Reading and Writing Text Files
- •“Tokenizing” Text
- •Byte Streams
- •Reading a Byte Stream
- •Data Streams
- •Writing to and Reading from Object Streams: Serialization
- •Serialization: Some More Details
- •Points to Remember
- •Summary
- •A Quick History of I/O APIs
- •Using the Path Interface
- •Getting Path Information
- •Comparing Two Paths
- •Using the Files Class
- •Checking File Properties and Metadata
- •Copying a File
- •Moving a File
- •Deleting a File
- •Walking a File Tree
- •Revisiting File Copy
- •Finding a File
- •Watching a Directory for Changes
- •Points to Remember
- •Summary
- •Introduction to JDBC
- •The Architecture of JDBC
- •Two-Tier and Three-Tier JDBC Architecture
- •Types of JDBC Drivers
- •Setting Up the Database
- •Connecting to a Database Using a JDBC Driver
- •The Connection Interface
- •Connecting to the Database
- •Statement
- •ResultSet
- •Querying the Database
- •Updating the Database
- •Getting the Database Metadata
- •Points to Remember
- •Querying and Updating the Database
- •Performing Transactions
- •Rolling Back Database Operations
- •The RowSet Interface
- •Points to Remember
- •Summary
- •Define the Layout of the JDBC API
- •Connect to a Database by Using a JDBC driver
- •Update and Query a Database
- •Customize the Transaction Behavior of JDBC and Commit Transactions
- •Use the JDBC 4.1 RowSetProvider, RowSetFactory, and RowSet Interfaces
- •Introduction to Exception Handling
- •Throwing Exceptions
- •Unhandled Exceptions
- •Try and Catch Statements
- •Programmatically Accessing the Stack Trace
- •Multiple Catch Blocks
- •Multi-Catch Blocks
- •General Catch Handlers
- •Finally Blocks
- •Points to Remember
- •Try-with-Resources
- •Closing Multiple Resources
- •Points to Remember
- •Exception Types
- •The Exception Class
- •The RuntimeException Class
- •The Error Class
- •The Throws Clause
- •Method Overriding and the Throws Clause
- •Points to Remember
- •Custom Exceptions
- •Assertions
- •Assert Statement
- •How Not to Use Asserts
- •Summary
- •Introduction
- •Locales
- •The Locale Class
- •Getting Locale Details
- •Resource Bundles
- •Using PropertyResourceBundle
- •Using ListResourceBundle
- •Loading a Resource Bundle
- •Naming Convention for Resource Bundles
- •Formatting for Local Culture
- •The NumberFormat Class
- •The Currency Class
- •The DateFormat Class
- •The SimpleDateFormat Class
- •Points to Remember
- •Summary
- •Introduction to Concurrent Programming
- •Important Threading-Related Methods
- •Creating Threads
- •Extending the Thread Class
- •Implementing the Runnable Interface
- •The Start( ) and Run( ) Methods
- •Thread Name, Priority, and Group
- •Using the Thread.sleep() Method
- •Using Thread’s Join Method
- •Asynchronous Execution
- •The States of a Thread
- •Two States in “Runnable” State
- •Concurrent Access Problems
- •Data Races
- •Thread Synchronization
- •Synchronized Blocks
- •Synchronized Methods
- •Synchronized Blocks vs. Synchronized Methods
- •Deadlocks
- •Other Threading Problems
- •Livelocks
- •Lock Starvation
- •The Wait/Notify Mechanism
- •Let’s Solve a Problem
- •More Thread States
- •timed_waiting and blocked States
- •waiting State
- •Using Thread.State enum
- •Understanding IllegalThreadStateException
- •Summary
- •Using java.util.concurrent Collections
- •Semaphore
- •CountDownLatch
- •Exchanger
- •CyclicBarrier
- •Phaser
- •Concurrent Collections
- •Apply Atomic Variables and Locks
- •Atomic Variables
- •Locks
- •Conditions
- •Multiple Conditions on a Lock
- •Use Executors and ThreadPools
- •Executor
- •Callable, Executors, ExecutorService, ThreadPool, and Future
- •ThreadFactory
- •The ThreadLocalRandom Class
- •TimeUnit Enumeration
- •Use the Parallel Fork/Join Framework
- •Useful Classes of the Fork/Join Framework
- •Using the Fork/Join Framework
- •Points to Remember
- •Summary
- •Using java.util.concurrent Collections
- •Applying Atomic Variables and Locks
- •Using Executors and ThreadPools
- •Using the Parallel Fork/Join Framework
- •Chapter 3: Java Class Design
- •Chapter 4: Advanced Class Design
- •Chapter 5: Object-Oriented Design Principles
- •Chapter 6: Generics and Collections
- •Chapter 7: String Processing
- •Chapter 8: Java I/O Fundamentals
- •Chapter 9: Java File I/O (NIO.2)
- •Chapter 10: Building Database Applications with JDBC
- •Chapter 11: Exceptions and Assertions
- •Chapter 12: Localization
- •Chapter 13: Threads
- •Chapter 14: Concurrency
- •OCPJP7 Exam (1Z0-804 a.k.a. Java SE 7 Programmer II) Topics
- •OCPJP 7 Exam (1Z0-805, a.k.a. Upgrade to Java SE 7 Programmer) Topics
- •Answers and Explanations
- •Answer Sheet
- •Answers and Explanations
- •Index
chapter 9 ■ Java File I/O (NIO.2)
•The take() method returns a queued key if available; otherwise it waits until a key is available.
•The key difference between the poll() and take() methods is that poll() is a non-blocking call and take() is a blocking call.
•When a key is returned, one or more events might be queued; that’s why you put in another for loop to iterate through all the available events.
•You can get the kind of event using the kind() method and the name of the file for which the event has occurred using the context() method.
•Once you are done with event processing, you need to reset the key using the reset() method on the key.
Points to Remember
Here are the concepts you need to understand in order to pass this section of the OCPJP exam.
•Do not confuse File with Files, Path with Paths, and FileSystem with FileSystems: they are different. File is an old class (Java 4) that represents file/directory path names, while Files was introduced in Java 7 as a utility class with comprehensive support for I/O APIs. The Path interface represents a file/directory path and defines a useful list of methods. However, the Paths class is a utility class that offers only two methods (both to get the Path object). FileSystems offer a list of factory methods for the class FileSystem, whereas FileSystem provides a useful set of methods to get information about a file system.
•The file or directory represented by a Path object might not exist.
•You learned how to perform a copy for files/directories. However, it is not necessary that you perform copy on two files/directories only. You can take input from an InputStream and write to a file, or you can take input from a file and copy to an OutputStream.
Methods copy(InputStream, Path, CopyOptions. . .) and copy(Path, OutputStream, CopyOptions. . .) could be used here.
•You must be careful about performing an operation when walking a file tree. For instance, if you are performing a recursive delete, you should first delete all the containing files before deleting the directory that is holding these containing files.
•The Visitor design pattern is used to enable walking through a file tree.
•In the context of a watch service, a state is associated with a watch key. A watch key might be in ready state (ready to accept events), in signed state (when one or more events are queued), or in invalid state (when the watch key is not valid). If the key is in the signed state, it is required to call the reset() method; otherwise the state of the key will not change to ready state and you will not receive any further event notification.
•Your program may receive an OVERFLOW event even if the program is not registered for this event.
•If you are watching a directory using the watch service offered by Java 7, then only files contained in that directory will be watched—and not the files contained in the subdirectories of that directory. If you intend to watch the whole subtree of the file system, you need to recursively register each directory in the subtree.
276

chapter 9 ■ Java File I/O (NIO.2)
Question Time!
1. Consider the following program:
import java.nio.file.*; |
|
|
|
public class PathInfo { |
|
public static void main(String[] args) { |
|
Path aFilePath = Paths.get("D:\\dir\\file.txt"); |
// FILEPATH |
|
|
while(aFilePath.iterator().hasNext()) {
System.out.println("path element: " + aFilePath.iterator().next());
}
}
}
Assume that the file D:\dir\file.txt exists in the underlying file system. Which one of the following options correctly describes the behavior of this program?
A)The program gives a compiler error in the line marked with the comment FILEPATH because the checked exception FileNotFoundException is not handled.
B)The program gives a compiler error in the line marked with the comment FILEPATH because the checked exception InvalidPathException is not handled.
C)The program gets into an infinite loop printing “path element: dir” forever.
D)The program prints the following: path element: dir
path element: file.txt
Answer: C) The program gets into an infinite loop printing “path element: dir” forever.
(In the while loop, you use iterator() to get a temporary iterator object. So, the call to next() on the temporary variable is lost, so the while loop gets into an infinite loop. In other words, the following loop will terminate after printing the “dir” and “file.txt” parts of the path:
Iterator<Path> paths = aFilePath.iterator(); while(paths.hasNext()) {
System.out.println("path element: " + paths.next());
}
Option A) is wrong because the Paths.get method does not throw FileNotFoundException.
Option B) is wrong because InvalidPathException is a RuntimeException. Also, since the file path exists in the underlying file system, this exception will not be thrown when the program is executed.
Option D) is wrong because the program will get into an infinite loop).
2.Which two of the following statements are correct regarding the SimpleFileVisitor interface?
A)The postVisitDirectory method, declared in SimpleFileVisitor, will be invoked after all the entries (i.e., files and subdirectories) of the directory have been visited.
277
chapter 9 ■ Java File i/O (NiO.2)
B) the visitFile method, declared in SimpleFileVisitor, will be invoked when a file is visited.
c)the visitFileOrDirectory method, declared in SimpleFileVisitor, will be invoked when a file or subdirectory is visited.
D) the walkFileTree method, declared in SimpleFileVisitor, will walk the file tree. Answer: a) and B) are correct statements.
(regarding option c), there is no such method as visitFileOrDirectory in SimpleFileVisitor interface. regarding option D), the walkFileTree method is a static method defined in the Files class that will walk the file tree. the walkFileTree method is not declared in SimpleFileVisitor. in fact, FileVisitor is one of the arguments this method takes for which you can pass a SimpleFileVisitor object as an argument.)
3.consider the following program: import java.nio.file.*;
class Relativize {
public static void main(String []args) { Path javaPath =
Paths.get("D:\\OCPJP7\\programs\\NIO2\\src\\Relativize.java").normalize(); Path classPath =
Paths.get("D:\\OCPJP7\\programs\\NIO2\\src\\Relativize.class").normalize();
Path result = javaPath.relativize(classPath); if(result == null) {
System.out.println("relativize failed"); } else if(result.equals(Paths.get(""))) {
System.out.println("relative paths are same, so relativize returned empty path");
} else {
System.out.println(result);
}
}
}
Which of the following options correctly shows the output of this program? a) the program prints the following: relativize failed.
B) the program prints the following: relative paths are same, so relativize returned empty path. c) the program prints the following: ..\relativize.class.
D) the program prints the following: ..\relativize.java.
Answer: c) the program prints the following: ..\relativize.class.
(the relativize() method constructs a relative path between this path and a given path. in this case, the paths for both the files are the same and they differ only in the file names (Relativize. java and Relativize.class). the relative comparison of paths is performed from the given path to the passed path to the relativize method, so it prints ..\relativize.class.
Note: the normalize() method removes any redundant name elements in a path. in this program, there are no redundant name elements, so it has no impact on the output of this program.)
278

chapter 9 ■ Java File I/O (NIO.2)
4.Consider the following program:
import java.nio.file.*;
class SubPath {
public static void main(String []args) {
Path aPath = Paths.get("D:\\OCPJP7\\programs\\..\\NIO2\\src\\.\\SubPath.java"); aPath = aPath.normalize();
System.out.println(aPath.subpath(2, 3));
}
}
This program prints the following:
A)..
B)src
C)NIO2
D)NIO2\src
E)..\NIO2
Answer: B) src
(The normalize() method removes redundant name elements in the given path, so after the call to the normalize() method, the aPath value is D:\OCPJP7\NIO2\src\SubPath.java.
The subpath(int beginIndex, int endIndex) method returns a path based on the values of beginIndex and endIndex. The name that is closest to the root has index 0; note that the root itself (in this case D:\) is not considered as an element in the path. Hence, the name elements “OCPJP7”, “NIO2”, “src”, “SubPath.java” are in index positions 0, 1, 2, and 3, respectively.
Note that beginIndex is the index of the first element, inclusive of that element; endIndex is the index of the last element, exclusive of that element. Hence, the subpath is “sub”, which is at index position 2 in this path.)
5.Assuming that the variable path points to a valid Path object, which one of the following statements is the correct way to create a WatchService?
A)WatchService watchService = WatchService.getInstance(path);
B)WatchService watchService = FileSystem.newWatchService();
C)WatchService watchService = path.getFileSystem().newWatchService();
D)WatchService watchService = FileSystem("default").getWatchService(path);
Answer: C) WatchService watchService = path.getFileSystem().newWatchService();
(The newWatchService() method is an abstract method defined in the FileSystem class. To get a WatchService instance associated with a given path object, you need to first get the associated FileSystem object and call the newWatchService() method on that FileSystem object. Hence, option C) is the right answer.)
279