A can full of Beans (Questions)

[Gavin Tranter]

Ok, well two

Is a bean allowed and equals and hashCode method?
Do all fields in a bean have to have both getters and setters?

I am thinking its okto have equals and hashCode, and that you may wish to represent read only properties, and thus, not having a setter is acceptable.

Cant think of a case for having a setter but not a getter.

G

[Chandra Bhatt]

Cant think of a case for having a setter but not a getter.

public class MrBeans {
    public void setName(String name) {
        this.name = name;
    }
 
    public String toString() {
        return "Name : " + name;
    }
 
private String name;
 
 
public static void main(String... args) {
    MrBeans mb = new MrBeans();
    mb.setName("MrBeans");
    System.out.println(mb); //prints MrBeans    
    
}
} 

This example may lend you a sapling of giant orchard.

Regards,
cmbhatt
[ April 11, 2007: Message edited by: Chandra Bhatt ]

[Jesper de Jong]

"Is a bean allowed and equals and hashCode method?"

Yes, a bean is just a class, just like any other class, so it can have an equals and hashCode method - in fact it might even be a good idea to provide these methods.

"Do all fields in a bean have to have both getters and setters?"

No, only the fields that you want to expose to the world outside the bean. The bean might have fields that are for internal use only. And indeed you can have read-only properties for which you only provide a getter and no setter.

[Gavin Tranter]

Thanks guys,
For some reason I find beans Intimidating.

[Stuart Ash]

Avoid the Heinz one and you ll be fine