Course contentsShow
← Java
Lesson 2344 of 2,87045. Reflection APIFree lesson

Invoking Static Methods Reflectively

Passing null as the first argument to invoke when calling static methods through reflection.

Invoking Static Methods Reflectively

What you'll learn: How to use invoke() to call static methods through reflection by passing null as the target object.

When you invoke a regular instance method reflectively, you pass the specific object you want to call the method on. But static methods don't belong to any particular instance—they belong to the class itself. So what object do you pass?

The null Argument Rule for Static Methods

When calling a static method through Method.invoke(), you pass null as the first argument. This makes sense: static methods don't need an instance to operate on, so there's no object to provide.

The general syntax looks like this:

Method staticMethod = MyClass.class.getMethod("myStaticMethod", parameterTypes);
Object result = staticMethod.invoke(null, arguments);

Why null Works

Think of it like calling a utility function. When you call Math.sqrt(16), you don't need a Math object—the method exists at the class level. Similarly, when invoking reflectively, you're telling the reflection API: "There's no instance involved here, just execute the class-level method."

Example

Class<?> mathClass = Math.class;
Method sqrtMethod = mathClass.getMethod("sqrt", double.class);

// Pass null for the target object since sqrt is static
Object result = sqrtMethod.invoke(null, 16.0);
System.out.println(result); // 4.0

Notice how null replaces where you'd normally put an instance reference. The reflection framework understands that for static methods, the first argument is irrelevant.

Key Takeaway: When invoking static methods reflectively with invoke(), always pass null as the first argument because static methods don't require an instance—they belong to the class itself.