Accessing static method

Bit of a newbie question but this has always baffled me and I have not been able to get a simple answer.

Just wonder why Netbeans moans about this code

Code :

---

frame = new JFrame();
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        frame.setDefaultLookAndFeelDecorated(true);

---

Why does it complain about accessing a static method?

When I ask it to change it, it does this:

frame = new JFrame();
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOS E);
JFrame.setDefaultLookAndFeelDecorated(true);

Which does not look right to me? (How would java know I am referring to the frame I am creating and not just frames in general).

I also note that net beans does not say anything when I do this

frame = new JFrame();
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOS E);
setDefaultLookAndFeelDecorated(true);

So which is correct here?

Hmm, I can't seem to spot the difference between any of the code you posted :P
Is your JFrame frame; declared outside of the main method?

Code :

---

frame.setDefaultLookAndFeelDecorated(true);

---

The above code is accessing a static method from an defined instance. It will still compile, but you will receive a warning. You should listen to your compiler, access static methods the correct way...by using the class name followed by the static variable/method.

Code :

---

JFrame.setDefaultLookAndFeelDecorated(true);

---

Bear in mind that we're talking about defaults, so it is ok to set these for frames in general (until you say otherwise).

If you check the reference, indeed setDefaultLookAndFeelDecorated() is static and setDefaultCloseOperation() isn't. Not sure why, but it is the case:
Java Platform SE 6

Your import javax.swing.JFrame; has to be what allows you to leave off the JFrame part. It wasn't completely clear to me that that always works when you have the import statement, but I'd say that's gotta be the reason why NetBeans doesn't complain.

Quote:

---

Originally Posted by aisthesis

Your import javax.swing.JFrame; has to be what allows you to leave off the JFrame part. It wasn't completely clear to me that that always works when you have the import statement, but I'd say that's gotta be the reason why NetBeans doesn't complain.

---

This is not true. Would have to see all of his code to know the reason. I would guess that the object that contains the method, that contains that code, is extending JFrame (or extending something that is extending JFrame).