
- •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)
if(args.length != 1){
System.out.println("usage: FileDelete <source-path>"); System.exit(1);
}
Path pathSource = Paths.get(args[0]); try {
Files.delete(pathSource); System.out.println("File deleted successfully");
} catch (IOException e) { e.printStackTrace();
}
}
}
It prints the following when executed:
D:\> java FileDelete log.txt File deleted successfully
There are a few points to remember when using the Files.delete() method. In the case of a directory, the delete() method should be invoked on an empty directory; otherwise the method will fail. In the case of a symbolic link, the link will be deleted, not the target file of the link. The file you intend to delete must exist; otherwise you will get a NoSuchFileException. If you silently delete a file and do not want to be bothered about this exception, then you may use the deleteIfExists() method, which will not complain if the file does not exist and deletes it if the file exists.
Walking a File Tree
In various situations, you need to walk through the file tree. For instance, when you want to search a specific file/ directory, you need to walk the file tree. Another example of when you need to walk a file tree is when you want to copy the whole directory containing files/subdirectories.
The Files class provides two methods that let you walk a file tree; the signatures of these methods are given here:
Path walkFileTree(Path start, FileVisitor<? super Path> visitor)
Path walkFileTree(Path start, Set<FileVisitOption> options, int maxDepth, FileVisitor<? super Path> visitor)
Both methods take a path from which the file tree walk will start and an instance of FileVisitor that will govern what you to do while walking a file tree. (We will talk about FileVisitor in detail shortly.) In addition, the second method takes two more parameters: file visit options and maximum depth. The maximum depth parameter specifies the depth of the file tree you wish to visit; a 0 value indicates only the specified file and a MAX_VALUE indicates that all levels of directories must be visited.
Note that you need to supply a FileVisitor instance to the walkFileTree() methods. The FileVisitor interface allows you to perform certain operations at certain key junctures. For instance, the interface provides a visitFile()method that you can implement to specify exactly what needs to be done when the FileVisitor
instance visits a file. Similarly, it also provides three more useful methods, which can be customized based on your needs: preVisitDirectory(), postVisitDirectory(), and visitFileFailed(). Table 9-3 provides a short summary of these methods.
267

chapter 9 ■ Java File i/O (NiO.2) |
|
Table 9-3. Methods Supported by the FileVisitor Interface |
|
|
|
Method |
Description |
FileVisitResult preVisitDirectory(T dir, BasicFileAttributes |
Invoked just before the elements of the |
attrs) |
directory are accessed. |
FileVisitResult visitFile(T file, BasicFileAttributes attrs) |
Invoked when a file is visited. |
FileVisitResult postVisitDirectory(T dir, IOException exc) |
Invoked when all the elements of the |
|
directory are accessed. |
FileVisitResult visitFileFailed(T file, IOException exc)
Invoked when the file cannot be accessed.
You need to implement the FileVisitor interface so that you can create an instance of your implementation and pass it to the walkFileTree() methods. However, if you do not want to implement all four methods in the FileVisitor interface, you can simply extend your implementation from the SimpleFileVisitor class. In this way, you can simply override those methods that you want to customize.
Listing 9-12 contains an example so you can understand this more clearly. Assume that you want to print the file tree from a specific point.
Listing 9-12. FileTreeWalk.java
import java.io.IOException; import java.nio.file.*;
import java.nio.file.attribute.BasicFileAttributes;
class MyFileVisitor extends SimpleFileVisitor<Path> {
public FileVisitResult visitFile(Path path, BasicFileAttributes fileAttributes){ System.out.println("file name:" + path.getFileName());
return FileVisitResult.CONTINUE;
}
public FileVisitResult preVisitDirectory(Path path, BasicFileAttributes fileAttributes){ System.out.println("----------Directory name:" + path + "----------");
return FileVisitResult.CONTINUE;
}
}
public class FileTreeWalk {
public static void main(String[] args) { if(args.length != 1) {
System.out.println("usage: FileWalkTree <source-path>"); System.exit(−1);
}
Path pathSource = Paths.get(args[0]); try {
Files.walkFileTree(pathSource, new MyFileVisitor()); } catch (IOException e) {
e.printStackTrace();
}
}
}
268
chapter 9 ■ Java File I/O (NIO.2)
Let’s first execute this program and then understand how it works.
D:\> java FileTreeWalk ch9-13
----------Directory name: ch9-13----------
file name:.classpath file name:.project
----------Directory name: ch9-13\.settings----------
file name:org.eclipse.jdt.core.prefs
----------Directory name: ch9-13\bin----------
file name:FileTreeWalk.class file name:MyFileVisitor.class
----------Directory name: ch9-13\bin\Test----------
file name:log.txt
----------Directory name: ch9-13\src----------
file name:FileTreeWalk.class file name:FileTreeWalk.java file name:MyFileVisitor.class
----------Directory name: ch9-13\src\Test----------
file name:log.txt
We have executed this program with one directory. It printed all the files and directories contained in the given input directory. Now, here’s how it works:
•You define a FileVisitor, MyFileVisitor, in which you overrode two methods, visitFile() and preVisitDirectory(), of the SimpleFileVisitor class. In these methods you just printed the name (along with path in case of directory) of the file/directory.
•You then invoked walkFileTree() with an instance of MyFileVisitor.
•The walkFileTree() method starts from the specified input path. It invokes the visitFile() method when it visits a file, preVisitDirectory() just before it starts visiting the elements of a directory, postVisitDirectory() immediately after it finishes visiting all the elements of the directory, and visitFileFailed() in case any file/directory is not accessible.
•Here, since you have overridden two methods, you are able to print the file names and the path of the directories visited.
•One more thing that requires attention here is the FileVisitReturn value. You can control the flow of the walk using FileVisitReturn values. There are four types of different return values:
•CONTINUE: It indicates that the walk through the file tree should continue.
•TERMINATE: It indicates that the walk through the file tree should be terminated immediately.
•SKIP_SUBTREE: It indicates that the rest of the subtree should be skipped for the walking file tree.
•SKIP_SIBLINGS: It indicates that walking file tree should be stopped for the current directory and its sibling directories. If it is returned from the preVisitDirectory(), then the containing files/directories are not visited and the postVisitDirectory() is also not visited. If it is returned from visitFile(), then no further file in the directory is visited. If it is returned from the postVisitDirectory(), then siblings of the directory are
not visited.
269
chapter 9 ■ Java File I/O (NIO.2)
Revisiting File Copy
You saw how to copy a file from one location to another. However, you couldn’t perform a copy on an entire directory (and its files/subdirectories). Now you can walk through the file tree, making it easier to implement a copy program that can copy the entire directory along with containing elements. Listing 9-13 shows the program to do so.
Listing 9-13. FileTreeWalkCopy.java
import java.io.IOException; import java.nio.file.*;
import java.nio.file.attribute.*;
// Our File visitor implementation that performs copy class MyFileCopyVisitor extends SimpleFileVisitor<Path> {
private Path source, destination;
public MyFileCopyVisitor(Path s, Path d) { source = s;
destination = d;
}
public FileVisitResult visitFile(Path path, BasicFileAttributes fileAttributes) { Path newd = destination.resolve(source.relativize(path));
try {
Files.copy(path, newd, StandardCopyOption.REPLACE_EXISTING); } catch (IOException e) {
e.printStackTrace();
}
return FileVisitResult.CONTINUE;
}
public FileVisitResult preVisitDirectory(Path path, BasicFileAttributes fileAttributes) { Path newd = destination.resolve(source.relativize(path));
try {
Files.copy(path, newd, StandardCopyOption.REPLACE_EXISTING); }catch (IOException e) {
e.printStackTrace();
}
return FileVisitResult.CONTINUE;
}
}
public class FileTreeWalkCopy {
public static void main(String[] args) { if(args.length != 2) {
System.out.println("usage: FileTreeWalkCopy <source-path> <destination-path>"); System.exit(1);
}
Path pathSource = Paths.get(args[0]); Path pathDestination = Paths.get(args[1]); try {
Files.walkFileTree(pathSource, new MyFileCopyVisitor(pathSource, pathDestination)); System.out.println("Files copied successfully!");
270