Attribute or private field and getter and Setter in Java object-oriented programming

Question

In object-oriented programming in Java, when I create any attribute or private field, without their respective methods getter and setter has to define the attribute as final or need not?

For example:

public class Pessoa {

    private String nome;
    private String endereco;
    private int idade;
    private double salario;

    public Pessoa(String nome, String endereco, int idade, double salario) {
        this.nome = nome;
        this.endereco = endereco;
        this.idade = idade;
        this.salario = salario;
    }

}

In this class above as you see, it lacks the methods getter and setter of the respective attributes or fields, in which case it would be necessary to define them as final?

Answer 1

Usually the field shouldn’t be final. It may be, but it rarely makes sense, and never when there’s one Setter. The final determines that the value cannot be changed after initializing in the constructor. Is this what you want? The field will be immutable when you do that, and then a Setter will have no function, unless do in it something completely meaningless since what normal would change the value of the field associated with it.

What you call attribute actually calls field. I know, it’s not your fault, everyone even teaches wrong. In English the correct terms are getter and Setter.

And I take this opportunity to say that these methods should not always be used, contrary to what many say. Yes, to be 100% object oriented you should use, but what people don’t say is that you don’t always have benefits doing this and always have some harm, you need to decide if it’s worth it. There’s a question where I Linko several questions on the subject, take a browse there: Getters and Setters Methods.

The original question had other conceptual problems, programming has a lot to do with conceptualizing things correctly, especially in object orientation which is to organize the concepts in a way that makes sense.