Why do setter methods in the Builder design pattern return `this`?

Question

I want to know why setter methods has return this; in it. What does it mean?

new Person().setName("alex");

[Method chaining - why is it a good practice, or not?](https://stackoverflow.com/q/1103985/1371329) — jaco0646, Aug 11 '22 at 22:37

score 1 · Answer 1 · edited Aug 12 '22 at 20:25

That's called a fluent interface.

The Builder pattern doesn't necessarily dictate that it has to be fluent, but that's often how it's implemented. It allows for users of the Builder to string together multiple calls (ie, "fluent"):

Persoon al = Person.builder()
            .setFirstName("Albert")
            .setLastName("Einstein")
            .setOccupation("Genius")
            .setGender(Gender.Male)
            .build();

score 0 · Answer 2 · answered Sep 30 '22 at 01:53

As already answered, it's not necessary, but it is the convention. And by using it, you can take advantage of the method chaining (Note that method chaining eliminates an extra variable for each intermediate step). You can see: Why is the usage of builder pattern highly encouraged instead of a straight forward implementation of fluent API in Java? and Using fluent interface with builder pattern

Why do setter methods in the Builder design pattern return `this`?

2 Answers2