Reputation: 1208
When trying to map nested Object using @Data and @Builder, mapStruct throw the following errors: "No read accessor found for property "profile" in target type."
@Mapper(componentModel = "spring")
public interface AuthMapper {
// only for testing mapping is working
@Mapping(target = "profile.organization", source = "organization")
RequestCreateOktaUser toEntity(Integer organization);
// only for testing mapping is working
@Mapping(target = "profile.login", source = "request.profile.email")
RequestCreateOktaUser toEntity(RequestMobilePreRegisterLocation.User request);
// Throw error "No read accessor found for property "profile" in target type" at compile time
@Mapping(target = "profile.organization", source = "organization")
@Mapping(target = "profile.login", source = "request.profile.email")
RequestCreateOktaUser toEntity(RequestMobilePreRegisterLocation.User request, Integer organization);
}
Model using Lombok simplified for simplicity
@Data
@NoArgsConstructor
@AllArgsConstructor(access = AccessLevel.PRIVATE)
@Builder
public class RequestCreateOktaUser {
private Profile profile;
@Data
@NoArgsConstructor
@AllArgsConstructor(access = AccessLevel.PRIVATE)
@Builder
public static class Profile {
private String login;
private String email;
private Integer organization;
}
}
@Data
@NoArgsConstructor
@AllArgsConstructor(access = AccessLevel.PRIVATE)
@Builder
public class RequestMobilePreRegisterUser {
@Valid
private User user;
@Data
@NoArgsConstructor
@AllArgsConstructor(access = AccessLevel.PRIVATE)
@Builder
public static class User {
@Valid
private Profile profile;
@Data
@NoArgsConstructor
@AllArgsConstructor(access = AccessLevel.PRIVATE)
@Builder
public static class Profile {
@NotEmpty
@Email
private String email;
}
}
The two first Mapping are working as expected, but when trying to combine the two the following errors is being thrown at compile time "No read accessor found for property "profile" in target type."
If someone could help me on this one I would really appreciate.
Thanks a lot,
Jonathan.
Upvotes: 7
Views: 13296
Reputation: 457
The best thing to do is avoiding nested mappings.
You may have separate method for nested mappings. so you can have a method to convert nested types first. for example user to profile.
Then you can use expression
to let mapstruct know which method it uses for nested mapping (not sure even if it's needed)
And if you have something else to map to the Profile (like organization) which is not part of nested source, you can use @AfterMapping
Upvotes: -1
Reputation: 631
Instead of ignoring the builder, we can add another mapper, say ProfileMapper
and then in the 'parent mapper' (e.g UserMapper
) you can use mapper annotation like this
@Mapper(uses = {ProfileMapper.class})
interface UserMapper {
...
}
Upvotes: 1
Reputation: 1208
solution:
@Mapper(componentModel = "spring", builder = @Builder(disableBuilder = true))
Upvotes: 33