Reference Variable vs Object in Java

Direct Answer

A reference variable holds either null or a reference to an object; it is not the object itself and Java does not expose it as a raw address. Several variables can refer to the same object, so a mutation through one reference is visible through the others. == tests reference identity, while equals() tests the equality policy defined by the class.

Code Example

public class ReferenceDemo {
    public static void main(String[] args) {

        Student s1 = new Student();
        s1.name = "Alice";
        s1.marks = 95;

        // s2 is a second reference to the SAME object — not a copy
        Student s2 = s1;

        s2.marks = 100;  // modifying through s2...

        System.out.println(s1.marks); // 100 — s1 sees the change too
        // Proof: s1 and s2 point to the same heap object

        // Null reference
        Student s3 = null;
        // s3.marks;  // NullPointerException — no object behind this reference

        // Comparing references with ==
        System.out.println(s1 == s2); // true — same object
        Student s4 = new Student();   // a brand new object
        System.out.println(s1 == s4); // false — different object, different object
    }
}

class Student {
    String name;
    int marks;
}

Common Mistakes & Pitfalls

• Treating the variable as the object — s1 is only the address; the real Student data lives on the heap, and saying "s1 is the student" hides every bug that comes from sharing.
• Expecting s2 = s1 to make a copy — it copies the reference, so both variables point at one object; modifying through s2 is instantly visible through s1.
• Comparing objects with == — == checks whether two references hold the same object, not whether the objects have equal content; use .equals() for content, and two separate new objects are == false even with identical fields.
• Calling a method on a null reference — s3.name when s3 is null throws NullPointerException; a declared reference is not an object until something is assigned to it.