How to add setter to Class using Lombok @Value

Question

@Value
@Builder
public class XXX {
    String field1;
    String field2;
    String field3;
}

I have a class using lombok @Value as above, where each field will be made private and final. Now, I'd like to have a setter for field3, which does not work because field3 is final. What should I do here?

IsaacD · Accepted Answer · 2022-11-02 16:07:58Z

7

I used @NonFinal and @Setter to achieve this without adjusting too much and staying in the lombok workflow.

I had a large model that I didn't want to refactor to have final variables on everything, so this was the simplest and cleanest solution for me.

@Value
@Builder
public class XXX {
    String field1;
    String field2;

    @NonFinal
    @Setter
    String field3;
}

answered Nov 2, 2022 at 16:07

IsaacD

3511 gold badge3 silver badges7 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Software Craftsman Over a year ago

Nice solution, helped me to achieve exactly what I wanted. Just as remark: @NonFinal is still an experimental feature at the moment.

Jan Rieke · Accepted Answer · 2018-11-09 09:37:07Z

4

Don't use @Value then. @Value is for value classes, i.e., classes whose instances are immutable. If you want a field to be mutable, then you clearly don't have a value class.

Instead, make all other fields final manually. Then use @Getter and @RequiredArgsConstructor (and @EqualsAndHashCode if required) on the class, and @Setter on all non-final fields. (Or use @Data, but carefully read its documentation.)

edited Nov 9, 2018 at 9:37

answered Nov 9, 2018 at 6:00

Jan Rieke

8,2723 gold badges23 silver badges37 bronze badges

2 Comments

LookIntoEast Over a year ago

I tried this, but it seems Getter+Setter+AllArgsConstructor is not sufficient. It keeps bugging. Documentation said: "In practice, Value is shorthand for: final ToString EqualsAndHashCode AllArgsConstructor FieldDefaults(makeFinal = true, level = AccessLevel.PRIVATE) Getter". So maybe I should add all these annotations?

LookIntoEast Over a year ago

Solved by adding EqualsAndHashCode

yyk · Accepted Answer · 2018-11-09 05:50:28Z

-2

Why is the field3 final? When a variable is declared with final keyword, its value can’t be modified, essentially, a constant. You should remove it!

Here you set the properties when you create the object

XXX s= XXX.builder().field1("XX").field2("XX").field3("XX").build(); setter are not needed here

edited Nov 9, 2018 at 5:50

answered Nov 9, 2018 at 2:39

yyk

11 bronze badge

1 Comment

LookIntoEast Over a year ago

Because all fields will be made as final by @Value; so what changes to make for annotations so that we could specifically make field3 NOT final and have a setter for it?

Collectives™ on Stack Overflow

How to add setter to Class using Lombok @Value

3 Answers 3

1 Comment

2 Comments

Why is the field3 final? When a variable is declared with final keyword, its value can’t be modified, essentially, a constant. You should remove it!

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

2 Comments

Why is the field3 final? When a variable is declared with final keyword, its value can’t be modified, essentially, a constant. You should remove it!

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related