Due to the time frame the discussion cannot be exhausting and we will focus on two language features that exist in Java since its advent, namely the implications of reference semantics on object copying and comparison and the use of exceptions for error indication and error handling. 

COPYING AND COMPARISON.     Regarding object copying and comparison in Java we examine the semantics of clone() and equals(). Questionable implementations of these functions can be found galore (in the JDK, in popular textbooks, even in commercial applications). It turns out that correct and symmetric implementation of these two functions is a non-trivial task. We will look into the details. 

EXCEPTION HANDLING.    Use of exceptions is mandatory in Java and cannot be avoided, yet in practice they are often misunderstood. We explain why and when one would want to handle exceptions at all (a common misunderstanding is that every potential exception must be caught.) We discuss common problems such as exception hiding, improper use of throws specification, and resource leaks and inconsistent object state.

Copying and Comparison of Objects (ca. 90 min)

Recap of reference semantics vs. value semantics
The semantic meaning of equals() 
The problem of asymmetric implementations in class hierarchies
Discussion of conceivable solutions
The semantic meaning of clone()
Shallow vs. deep copying 
Discussion of various solutions and related issues 

Exception Handling (ca. 90 min)

Recap of the language means
finally and its impact on control flow
Problematic throws clause
Hiding of exceptions
Maintaining valid object state and avoiding resource leaks
Reasons for catching and handling an exception