Why Default access modifier in Java? - Purpose & Use Cases

The Big Idea

What if your code could protect itself automatically without you writing extra rules?

The Scenario

Imagine you have many classes in your Java project, and you want some of them to share information only within the same package. Without a clear way to control access, you might try to write extra code to check who can see what, or you might accidentally expose sensitive parts to the whole world.

The Problem

Manually controlling access by writing extra checks or comments is slow and error-prone. You might forget to protect something important, or make your code too restrictive, causing bugs. It's like leaving your house door open because you forgot to lock it, or locking every door so tightly that even family members can't enter.

The Solution

The default access modifier in Java solves this by automatically restricting access to classes and members within the same package. It's a simple, built-in way to keep your code organized and safe without extra work. You just leave out the access keyword, and Java knows to keep it package-private.

Before vs After

✗ Before

public class MyClass {
    int data; // no modifier, but unclear access
}
// Need extra comments or checks to control access

✓ After

class MyClass {
    int data; // default access: visible only in the same package
}

What It Enables

This lets you design clean, modular code where parts can share data safely inside a package but stay hidden from the outside world.

Real Life Example

Think of a team working on a project where some tools are shared only among team members (same package), but not exposed to clients or other teams. Default access modifier helps enforce this naturally.

Key Takeaways

Default access modifier restricts visibility to the same package.

It avoids extra code for access control, reducing mistakes.

Helps keep code organized and secure within packages.

Practice

1. Which statement best describes the default access modifier in Java?

easy

A. It restricts access only to the class itself.

B. It allows access from any package using the default keyword.

C. It allows access only within the same package without using any keyword.

D. It allows access only to subclasses in other packages.

Solution

1. Step 1: Understand default access modifier meaning

   The default access modifier means no keyword is used before a class, method, or variable, and it restricts access to the same package only.

2. Step 2: Compare options with definition

   It allows access only within the same package without using any keyword. correctly states it allows access only within the same package and requires no keyword. Other options mention keywords or access outside the package, which is incorrect.

3. Final Answer:

   It allows access only within the same package without using any keyword. -> Option C

4. Quick Check:

   Default access = package-only access [OK]

Hint: No keyword means default access is package-only [OK]

Common Mistakes:

• Thinking default requires a keyword
• Confusing default with public or private
• Assuming default allows access from other packages

2. Which of the following is the correct way to declare a class with default access modifier?

easy

A. class MyClass {}

B. private class MyClass {}

C. default class MyClass {}

D. public class MyClass {}

Solution

1. Step 1: Recall syntax for default access modifier

   Default access means no access keyword is written before the class name.

2. Step 2: Check each option

   class MyClass {} declares the class without any access keyword, which means default access. Options A and B use explicit keywords, and C uses a non-existent keyword.

3. Final Answer:

   class MyClass {} -> Option A

4. Quick Check:

   No keyword = default access [OK]

Hint: No keyword before class means default access [OK]

Common Mistakes:

• Using 'default' keyword which does not exist in Java
• Confusing private with default
• Always using public by habit

3. Consider two classes in the same package:

class A {
    void show() {
        System.out.println("Hello from A");
    }
}

class B {
    public static void main(String[] args) {
        A a = new A();
        a.show();
    }
}

What will be the output when class B is run?

medium

A. Compile-time error: show() has private access

B. Hello from A

C. Compile-time error: class A is not public

D. Runtime error

Solution

1. Step 1: Analyze access modifiers in the code

   Class A and method show() have default access (no keyword). Both classes are in the same package, so access is allowed.

2. Step 2: Predict program output

   Since B can access A and its show() method, the program prints "Hello from A" without errors.

3. Final Answer:

   Hello from A -> Option B

4. Quick Check:

   Default access allows same package access [OK]

Hint: Default access works within same package [OK]

Common Mistakes:

• Assuming default means private access
• Thinking class A must be public to be used
• Confusing compile-time and runtime errors

4. Given two packages pkg1 and pkg2, and these classes:

package pkg1;
class C {
    void display() {
        System.out.println("Inside C");
    }
}

package pkg2;
import pkg1.C;
public class D {
    public static void main(String[] args) {
        C c = new C();
        c.display();
    }
}

What is the error in this code?

medium

A. Cannot access class C from pkg2 because it has default access

B. Cannot call display() because it is private

C. Cannot import package pkg1

D. No error, code runs fine

Solution

1. Step 1: Check class C's access modifier and package

   Class C has default access (no keyword) and is in package pkg1, so it is accessible only within pkg1.

2. Step 2: Check usage of C in pkg2

   Class D in pkg2 tries to create an instance of C and call display(), but C is not visible outside pkg1, causing a compile-time error.

3. Final Answer:

   Cannot access class C from pkg2 because it has default access -> Option A

4. Quick Check:

   Default access = package-only visibility [OK]

Hint: Default access blocks cross-package access [OK]

Common Mistakes:

• Assuming default access allows cross-package use
• Thinking display() is private
• Confusing import errors with access errors

5. You have a package tools with classes:

class Helper {
    void assist() {
        System.out.println("Helping...");
    }
}

public class Tool {
    public static void main(String[] args) {
        Helper h = new Helper();
        h.assist();
    }
}

You want to allow only classes inside tools to use Helper and its assist() method, but prevent access from outside. Which is the best way to achieve this?

hard

A. Make Helper and assist() public.

B. Use protected for Helper and assist().

C. Make Helper and assist() private.

D. Keep Helper and assist() with default access (no keyword).

Solution

1. Step 1: Understand access goals

   You want Helper and assist() accessible only inside the same package (tools) and hidden outside.

2. Step 2: Match access modifiers to goals

   Default access (no keyword) restricts access to the same package only, which fits the requirement. Public allows all access, private restricts to the class only, and protected allows subclasses and package access.

3. Final Answer:

   Keep Helper and assist() with default access (no keyword). -> Option D

4. Quick Check:

   Default access = package-only visibility [OK]

Hint: Default access hides from outside packages [OK]

Common Mistakes:

• Using public which exposes to all packages
• Using private which hides even inside package
• Using protected which allows subclass access outside package