Exceptions, cont’d. Factory Design Pattern COMP 401 Fall 2014 Lecture 12 9/30/2014

Midterm Curve Clarification about point value for multiple choice section. – Each questions worth 5 points. Each choice essentially graded as a T/F question. – Part 1 worth 15*5 = 75 points Not 45 as written in the exam. Exam Curve: – Raw Score Range: 61 – 127 – Average (StdDev): (15.06) – First normalize your raw score: N = (R – Average) / StdDev

Midterm Curve

Exception Trace Example lec12.exception

General Principle: Be Specific Use an existing exception type. – There are lots. – If semantics of the exception match well, then go ahead and use it. Create your own exception type. – Subclass either RuntimeException or Exception lec11.ex9.v1 – Notice how less specific general exception raised by Scanner transformed into context-specific exception for Playlist. – Also note how error message can be retrieved from exception object. See handling of PlaylistFormatError in main() See reference page for Exception for more. 5

General Principle: Catch Late Exceptions should rise to level where application has enough context to deal with them effectively. – Catching exception just because you can is not always the right thing to do. Pass the buck unless you know what to do. – Look again at lec11.ex9.v1 In particular, note handling of FileNotFoundException – lec11.ex9.v2 Note printStackTrace() method of Exception in Main1 Note differences in how FileNotFoundException handled in Main1 vs. Main2 6

General Principle: Throw Early Validate values as early as possible. – Rather than waiting for exception generated by invalid values sent to other code. Particularly apropos for null values that may later cause a NullPointerException Exception generated is not very specific Almost always have to look higher in the stack trace to see what the real problem is. lec11.ex9.v3 7

Odds and Ends Remember that the scope of a variable is limited to the surrounding block. – Sometimes an issue if you declare a variable inside a try block but then need its value outside of the try block later. Sibling catch blocks can reuse the same variable name for the declared error object. A catch block associated with an exception class cannot precede a catch block associated with a subclass. – Results in unreachable code. try-catch-finally blocks can be nested. Interfaces must declare any checked exceptions thrown by any of its implementations. Finally always runs – Even if you “return” from within a try or catch block – lec11.ex10

Factory Design Pattern When direct construction of an object is complicated or harmful – … or at least undesired – By “direct construction”, I mean by using the new keyword Several different contexts when factory design pattern is appropriate: – Singleton When there should only be one instance of a particular class in the whole system. – Multiton When there should only be one instance of of an object associated with some identifying property – Dynamic subclass binding When the specific subclass of an object can only be determined at the time that it is created – Complex construction When the construction of the object requires complex validation and/or side effects that must be handled. When null should be a valid result When an existing object might need to be provided instead of a new one.

The Basic Factory Pattern Make the constructor private – This prevents direct use of the new keyword for creating new objects outside of the class. Provide static class methods that construct new instances and return them. – These are the “factories” – Return type of the factory method is the same as the class. class FPClass { private FPClass() { // Private constructor } public static FPClass factoryMethod() { return new FPClass(); } FPClass o = FPClass.factoryMethod();

Singleton One Object To Rule Them All When there should only be one instance of a particular class in the whole system at any given time. – Generally the object represents some sort of system-wide resource that may be needed by many objects in different parts of the software. – Modifies basic factory pattern by maintaining a single instance. » Created on demand when first requested Lazy initiation » Stored in a private static variable and retrieved by a static getter Static getter is the factory method lec12.ex1 – Simple logging mechanism. lec12.ex2 – A variant that allows for singleton instance to be one of several subclasses.

Multiton Maintains a single instance of the object with regard to some uniquely identifying characteristic of object. Multiton factory method – Static (as per the general factory pattern) – Provided all info. needed to create a new object if necessary. – Determines if corresponding object already exists. If so, returns the existing object If not, creates the new object and inserts it into a static structure Usually implemented using a “map”

Map and HashMap Map is a collection of key/value pairs – Sometimes called a “dictionary” Java Collections Framework – Interface: Map – Implementation: HashMap – K and V are placeholders for type names K for the type of the key, and V for the type of the value. Must be reference types Basic operations: – Creating a new map Map m = new HashMap () – Inserting a value associated with a key m.put(key, value); – Retrieving a value associated with a key V value = m.get(key); – Checking to see if key already in the map m.containsKey(key); // Returns boolean – Removing a key/value pair from the map m.remove(key)

Multiton Example lec12.ex3 – Student is a class that models students Uniquely identified by PID property – getStudent() is factory method Notice that all info needed to create student is provided. – lookupStudent() is a factory method variant that only retrieves existing objects. Does not create object if it doesn’t exist (but must signal that fact) In example, this is done by returning null What would another option have been? lec12.ex4

Value Types In A Reference Type Context Integer reference type – Map can only work with reference types but the key we want to use is simple integer – Java provides reference type versions of basic value types for these kinds of situations. Integer, Double, Character Automatic “boxing” and “unboxing” – As of Java 1.7, can use value type where reference type is expected and Java will automatically “box” the value. – Similarly, will “unbox” a reference type to the value type when assigning to a value type variable.

Dynamic Subclass Binding Useful when choice needs to be made between several different subclasses – Leaves decision about which subclass to use to the factory method Factory method given any/all information that is relevant to decision and for creating new object if necessary. lec12.ex5

A rose by any other name Some design pattern textbooks / frameworks associate the name “Factory” specifically and only for dynamic subclass binding use case. – Other cases described as separate patterns In my presentation, I’ve grouped all of these use cases under the name “Factory” more generally. – Just something to be aware of if/when you encounter the term in tutorials/documentation/etc.