
- •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 6 ■ Generics and Collections
Now, how to get the characters from a String? Remember that array indexing doesn’t work for Strings. For example, to get the first character "t", if you use pangram[0] in the program, you’ll get a compiler error. Fortunately, String has a method called toCharArray() that returns a char[]. So, you use this method for traversing over the string and get all the characters. As you add the characters into the TreeSet, the characters are stored in a sorted order. So, you get all the lowercase letters when you print the set.
Note in the output that there is one leading comma. Why? The pangram string has many whitespace characters. One whitespace also gets stored in the set, so it also gets printed!
The Map Interface
A Map stores key and value pairs. The Map interface does not extend the Collection interface. However, there are methods in the Map interface that you can use to get classes in the Collection to work around this problem. Also, the method names in Map are very similar to the methods in Collection, so it is easy to understand and use Map. There are two important concrete classes of Map that we’ll cover: HashMap and TreeMap.
A HashMap uses a hash table data structure internally. In HashMap, searching (or looking up elements) is a fast operation. However, HashMap neither remembers the order in which you inserted elements nor keeps elements in any sorted order.
A TreeMap uses a red-black tree data structure internally. Unlike HashMap, TreeMap keeps the elements in sorted order (i.e., sorted by its keys). So, searching or inserting is somewhat slower than the HashMap.
The HashMap Class
Assume that you are implementing a simple spell checker. Given an input string, the spell checker looks for words that are usually misspelled; if there is a match, it prints the correct spelling. So, the spell checker should maintain a list of frequently misspelled words and their correct spellings. How can you implement this?
Given a key, you can look out for a value using a Map. Now, which map to use, HashMap or a TreeMap? There is no need (though you are able) to keep the misspelled words in sorted order, and the lookup for misspelled words should be very fast. So, HashMap is suitable for solving this problem.
Listing 6-18 is a simple program showing how to implement a spell checker.
Listing 6-18. SpellChecker.java
// This program shows the usage of HashMap class public class SpellChecker {
public static void main(String []args) {
Map<String, String> misspeltWords = new HashMap<String, String>(); misspeltWords.put("calender", "calendar"); misspeltWords.put("tomatos", "tomatoes"); misspeltWords.put("existance", "existence"); misspeltWords.put("aquaintance", "acquaintance");
String sentence = "Buy a calender for the year 2013"; System.out.println("The given sentence is: " + sentence); for(String word : sentence.split("\\W+")) {
if(misspeltWords.containsKey(word)) { System.out.println("The correct spelling for " + word
+ " is: " + misspeltWords.get(word));
}
}
}
}
181
Chapter 6 ■ Generics and Collections
It prints the following:
The given sentence is: Buy a calender for the year 2013 The correct spelling for calender is: calendar
First, you need to create a table of misspelled words and their correct spellings. Since both key and value are Strings, you create a HashMap<String, String> object. You insert four misspelled words and their correct spellings in the HashMap. The misspelled word is the key and the correct spelling is the value. You use the put() method (instead of the add() method you use in Container) for inserting a pair (a key and its value) into the Map.
You use the simple approach of separating the words in a sentence—you use String’s split() method. For each word, you check if the word is an exact match for the misspelled word; if so, you print the value matching that key. You use the containsKey() method for checking if the key exists in the map; it returns a Boolean value. You use the get() method to return the value from the map given the key as argument. Since the given sentence has one word misspelled (“calender”), you print the correct spelling for that word.
Now, let’s look at the keys in the misspeltWords HashMap. You can get all the keys in the HashMap using the keySet() method. Since you have HashMap<String, String>, the returned set is of type Set<String>.
Set<String> keys = misspeltWords.keySet(); System.out.print("Misspelt words in spellchecker are: "); System.out.println(keys);
It prints the following:
Mispelled words in spellcheker are: [calender, existance, aquaintance, tomatos]
Similarly, you can use valueSet() method to get the values available in the map.
Overriding the hashCode() Method
Overriding the equals and hashCode methods correctly is important for using the classes with containers (particularly, HashMap and HashSet). Listing 6-19 is a simple Circle class example so you can understand what can go wrong.
Listing 6-19. TestCircle.java
// This program shows the importance of equals() and hashCode() methods
import java.util.*;
class Circle {
private int xPos, yPos, radius; public Circle(int x, int y, int r) {
xPos = x; yPos = y; radius = r;
}
public boolean equals(Object arg) { if(arg == null) return false; if(this == arg) return true; if(arg instanceof Circle) {
Circle that = (Circle) arg;
182

Chapter 6 ■ Generics and Collections
if( (this.xPos == that.xPos) && (this.yPos == that.yPos) && (this.radius == that.radius )) {
return true;
}
}
return false;
}
}
class TestCircle {
public static void main(String []args) {
Set<Circle> circleList = new HashSet<Circle>(); circleList.add(new Circle(10, 20, 5)); System.out.println(circleList.contains(new Circle(10, 20, 5)));
}
}
It prints false (not true)! Why? The Circle class overrides the equals() method, but it doesn’t override the hashCode() method. When you use objects of Circle in standard containers, it becomes a problem. For fast lookup, the containers compare hashcode of the objects. If the hashCode() method is not overridden, then—even if an object with same contents is passed—the container will not find that object! So you need to override the hashCode() method.
Okay, how do you override the hashCode() method? In the ideal case, the hashCode() method should return unique hash codes for different objects.
The hashCode() method should return the same hash value if the equals() method returns true. What if the objects are different (so that the equals() method returns false)? It is better (although not required) for the
hashCode() to return different values if the objects are different. The reason is that it is difficult to write a hashCode() method that gives unique value for every different object.
The methods hashCode() and equals() need to be consistent for a class. For practical purposes, ensure that you follow this one rule: the hashCode() method should return the same hash value for two objects if the equals() method returns true for them.
When implementing the hashCode() method, you can use the values of the instance members of the class to create a hash value. Here is a simple implementation of the hashCode() method of the Circle class:
public int hashCode() {
//use bit-manipuation operators such as ^ to generate close to unique hash codes
//here we are using the magic numbers 7, 11 and 53, but you can use any numbers,
preferably primes |
return (7 * xPos) ^ (11 * yPos) ^ (53 * yPos); |
} |
|
|
|
Now if you run the main() method, it prints “true”. In this implementation of the hashCode() method, you multiply the values by a prime number as well as bit-wise operation. You can write complex code for hashCode() if you want a better hashing function, but this implementation is sufficient for practical purposes.
183

Chapter 6 ■ Generics and Collections
You can use bitwise operators for int values. What about other types, like floating-point values or reference types? To give you an example, here is hashCode() implementation of java.awt.Point2D, which has floating point values x and y. The methods getX() and getY() return the x and y values respectively:
public int hashCode() {
long bits = java.lang.Double.doubleToLongBits(getX()); bits ^= java.lang.Double.doubleToLongBits(getY()) * 31; return (((int) bits) ^ ((int) (bits >> 32)));
}
This method uses the doubleToLongBits() method, which takes a double value and returns a long value. For floating-point values x and y (returned by the getX and getY methods), you get long values in bits and you use bit-manipulation to get hashCode().
Now, how do you implement the hashCode method if the class has reference type members? For example, consider using an instance of Point class as a member instead of xPos and yPos, which are primitive type fields:
class Circle {
private int radius; private Point center; // other members...
}
In this case, you can use call the hashCode() method of Point to implement Circle’s hashCode method:
public int hashCode() {
return center.hashCode() ^ radius;
}
If you’re using an object in containers like HashSet or HashMap, make sure you override the hashCode() and equals() methods correctly. If you don’t, you’ll get nasty surprises (bugs) while using these containers!
The NavigableMap Interface
The NavigableMap interface extends the SortedMap interface. In the Collection hierarchy, the TreeMap class is the widely used class that implements NavigableMap. As the name indicates, with NavigableMap, you can navigate the Map easily. It has many methods that make Map navigation easy. You can get the nearest value matching the given key, all values less than the given key, all values greater than the given key, etc. Let’s look at an example: Lennon, McCartney, Harrison, and Starr have taken an online exam. In that exam, the maximum they can score is 100, with a passing score of 40. If you want to find details such as who passed the exam, and sort the exam scores in ascending or descending order, NavigableMap is very convenient (see Listing 6-20).
184