Important Notice - Forums is archived
To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
Lombok working in Vaadin?
Hi,
I am doing the project with Vaadin-Spring addon. In order to cut down the repeative codes, I use lombok.
I wonder if lombok is compatible with Vaadin.
The codes are;
package za.dash.domain
@Entity
@Getter
@Setter
@Table(name = "group_members")
public class GroupMembers extends AbstractEntity {
@Column(name = "user_id")
private Long userId;
@ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "user_id", referencedColumnName = "id", nullable = false, insertable = false, updatable = false)
private Users usersByUserId;
..........
}
package za.dash.ui.views;
@Secured({"ROLE_ADMIN"})
@SpringView(name = "groupmembers")
public class GroupMembersView extends CustomComponent implements View {
@Autowired
private final GroupMembersRepository groupMembersRepository;
.........
private void addnewRecord() {
try {
Long userchangedid = Long.valueOf(0);
GroupMembers groupMembers = new GroupMembers();
groupMembers.setUserId(idusers);
groupMembers.setGroupId(idgroups);
groupMembers.setUserChanged(userchangedid);
groupMembersRepository.save(groupMembers);
refresh();
} catch (Exception e) {
logger.debug("addnewRecord "+e.getMessage()+" UsersId "+idusers+" GroupsId "+idgroups);
}
}
.......
When I compile, the message comes out saying
"Error:(250, 25) java: cannot find symbol
symbol: method setUserId(java.lang.Long)
location: variable groupMembers of type za.dash.core.domain.GroupMembers"
I code manually as below
private Long getUserId() { return userId; }
private void setUserId(long userId) { this.userId = userId; }.
It compiles without error.
Regards,
Michael
Hi,
it works for me here - so I guess it is compatible.
Best Regards,
Frank
Please ignore my message. It is fixed.
It is due to the configuration of IntelliJ IDEA.
Thank you.
Regards,
Michael