Course contentsShow
← Java
Lesson 676 of 2,87016. Packages, Imports, and JAR FilesFree lesson

What Is a Fully Qualified Name (FQN)?

Learn how FQNs uniquely identify classes by combining package and class names.

What Is a Fully Qualified Name (FQN)?

You'll learn: How Java uniquely identifies every class using its complete package path and class name.

The Core Idea

A Fully Qualified Name (FQN) is the complete, unambiguous name of a class that includes its entire package hierarchy followed by the class name itself. It's like a postal address for your code—specific enough that Java can locate exactly which class you mean, even if multiple classes share the same simple name.

Understanding FQNs

The FQN combines two parts:

  1. The package name (the full path, with dot separators)
  2. The class name (the simple identifier)

Format: package.name.ClassName

Examples

  • java.util.ArrayList — package is java.util, class is ArrayList
  • java.sql.Date — package is java.sql, class is Date
  • java.util.Date — package is java.util, class is also Date

Notice the last two examples? Both are called Date, but their FQNs make them distinct. Without FQNs, Java couldn't tell them apart.

Why FQNs Matter

When you use import statements, you're essentially telling Java: "When I write ArrayList, I really mean java.util.ArrayList." But you can always bypass imports and write the FQN directly:

java.util.ArrayList<String> list = new java.util.ArrayList<>();

This is verbose but eliminates any ambiguity, especially useful when you need classes with conflicting simple names in the same file.

The Analogy

Think of FQNs like full street addresses. "Main Street" exists in thousands of towns, but "123 Main Street, Springfield, IL 62701" points to exactly one location. Similarly, Date is ambiguous, but java.util.Date is precise.

Key Takeaway: A Fully Qualified Name uniquely identifies a class by combining its complete package path with its class name, ensuring no ambiguity even when multiple classes share the same simple name.