Interface Fields

[Naresh Chaurasia]

What is the reason of having fields as static and final in interfaces?

[Seetharaman Venkatasamy]

because interface can not have implementation

[Mo Jay]

SCJP 1.4

Again Naresh Chaurasia , you are supposedly already certified therefore you shouldn't be asking basic questions like these that were part of your preparation for the SCJP exam in the first place. I Also noticed in another thread that you asked another basic question regarding checked/unchecked exception, these make me wonder how did you become SCJP and what did you use as a study material if any.

[Devaka Cooray]

Mo Jay wrote:

SCJP 1.4

Again Naresh Chaurasia , you are supposedly already certified therefore you shouldn't be asking basic questions like these that were part of your preparation for the SCJP exam in the first place.

Cooldown I think he need to upgrade his certification to the latest version, and might need to focus on some topics like this. Anyway, anyone can ask any SCJP-related question here.

Devaka.

[Muhammad Khojaye]

Naresh Chaurasia wrote:What is the reason of having fields as static and final in interfaces?

Also remember, interface serves as a type which means the class that implement an interface say something about what a client can do with instances of the class, which become inappropriate when you use interface only for defining constants.

[Seetharaman Venkatasamy]

Muhammad Ali Khojaye wrote:
interface serves as a type which means the class that implement an interface say something about what a client can do with instances of the class, which become inappropriate when you use interface only for defining constants.

Exactly . use final class to define the constants.giving a private constructor makes sense