Is it possible to make methods non-virtual in Java?

i am newbie in java and i usually used c++ i just wondering this code works

public class ParentClass {
    public void methodA() {
        System.out.println("This is Parent A Method");
        whoAmI();
    }

    public void methodB() {
        System.out.println("This is Parent B Method and I am Calling Method A");
        whoAmI();
        methodA();
    }
}

public class ChildClass extends ParentClass{
    @Override
    public void methodA() {
        System.out.println("This is Child A Method and I am Calling Parents Method A");
        whoAmI();
        super.methodA();
    }

    @Override
    public void methodB() {
        System.out.println("This is Child B Method and I am Calling Parents Method B");
        whoAmI();
        super.methodB();
    }
}

ChildClass c = new ChildClass();
c.methodB();

and I expected output like this

This is Child B Method and I am Calling Parents Method B
This is Parent B Method and I am Calling Method A
This is Parent A Method

but was

This is Child B Method and I am Calling Parents Method B
This is Parent B Method and I am Calling Method A
This is Child A Method and I am Calling Parents Method A
This is Parent A Method

so i realized that in java all non-static methods are by default virtual functions like virtual keyword in c++.

is there any way to make output like this?

This is Child B Method and I am Calling Parents Method B
This is Parent B Method and I am Calling Method A
This is Parent A Method

You can wrap the methodA's impl of ParentClass in a seperate private method:

public class ParentClass {
    public void methodA() {
        interMethodA();
    }

    private void interMethodA() {
        System.out.println("This is Parent A Method");
        whoAmI();
    }

    public void methodB() {
        System.out.println("This is Parent B Method and I am Calling Method A");
        whoAmI();
        interMethodA();
    }
}

And the ChildClass remains the same.

The code - as is - does not compile since method whoAmI() is undefined. By removing the calls to this method, I was able to reproduce the output.

From what I understand, you want to ensure that methodA in Parent is called from methodB in Parent. Since dynamic dispatching is used in Jjava to determine which actual implementation is called, we have to enforce that methodA cannot be overridden. As @MarquisofLorne pointed out, C++ uses dynamic dispatch aswell, if methodA is defined as virtual in Parent.

To enforce that dynamic dispatch always results in a call to Parent's methodA, there are two general approaches that come to my mind: declaring methodA as final and declaring methodA as private.

Approach one: declare methodA in Parent as final

When going down this route, Child cannot re-define methodA, i.e. the code would result in a compile-time error if methodA is not removed from Child.

<kbd>Ideone demo</kbd>

Approach two: declare methodA in Parent as private

This approach is similar to the first approach, but allows you to retain methodA in Child, albeit the @Override-annotation must be removed since private methods cannot be overridden.

<kbd>Ideone demo</kbd>

You got:

This is Child B Method and I am Calling Parents Method B
This is Parent B Method and I am Calling Method A
This is Child A Method and I am Calling Parents Method A
This is Parent A Method 

Instead of

This is Child B Method and I am Calling Parents Method B
This is Parent B Method and I am Calling Method A
This is Parent A Method

Simply Bacause, In Java calling methodA() or this.methodA() in your methodB() of ParentClass calls the method off of the calling object or instance, Yet the instance is an instanceof ChildClass. Java treats methodA() and this.methodA() as same. The this keyword in Java actually refers to the "currently running instance of the object you're using". Meaning, the overridding methodA() of ChildClass will be called instead of methodA() of ParentClass.

Here is a suggestion, to get the expected output, simply apply modifications on the overridding methodA() of ChildClass by commenting out the printing line.
Otherwise reference this for more details.