spring JPA用户、角色身份验证-如何避免重复的角色条目？

Question

import java.util.Set;

import javax.persistence.*;

@Entity
public class User {

    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private long id;

    private String email;

    private String password;

    public long getId() {
        return id;
    }

    public void setId(long id) {
        this.id = id;
    }

    public String getEmail() {
        return email;
    }

    public void setEmail(String email) {
        this.email = email;
    }

    public String getPassword() {
        return password;
    }

    public void setPassword(String password) {
        this.password = password;
    }

    public Set<Role> getRoles() {
        return roles;
    }

    public void setRoles(Set<Role> roles) {
        this.roles = roles;
    }

    @ManyToMany(fetch = FetchType.EAGER,cascade = CascadeType.ALL)
    @JoinTable(joinColumns = @JoinColumn(name = "id"),inverseJoinColumns = @JoinColumn(name = "roleId"))
    private Set<Role> roles;

    public User(String email, String password, Set<Role> roles) {
        super();
        this.email = email;
        this.password = password;
        this.roles = roles;
    }

}

角色

 import java.util.Set;

import javax.persistence.Entity;
import javax.persistence.FetchType;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;
import javax.persistence.ManyToMany;

@Entity
public class Role {

    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private long id;

    private String role;

    @ManyToMany(mappedBy = "roles",fetch = FetchType.LAZY)
    private Set<User> users;

    public Role(String role) {
        super();
        this.role = role;
    }

    public long getId() {
        return id;
    }

    public void setId(long id) {
        this.id = id;
    }

    public String getRole() {
        return role;
    }

    public void setRole(String role) {
        this.role = role;
    }

    public Set<User> getUsers() {
        return users;
    }

    public void setUser(Set<User> users) {
        this.users = users;
    }



}

Answer 1

manytomany是正确的逻辑关系类型。获得太多角色的原因可能是创建了Role的新实例，但如果数据库中已经存在该角色，则必须将其加载到持久性上下文中，只有在不存在时才创建新角色。

如果您用代码管理事务，那么它将如下所示，如果您使用@transactional的容器管理持久性，则应该删除事务代码和try-finally块。

try {
    List<String> roleNames = Lists.newArrayList("user, admin, superuser");
    User user = new User("Peter", "Pan");
    List<Role> roles = new ArrayList<>();
    entityManager.getTransaction().begin();
    for (String roleName : roleNames) {
        List<Role> found = entityManager.createQuery("select r from Roles r where r.name = :roleName", Role.class)
                .setParameter("roleName", roleName).getResultList();
        if (found.isEmpty()) {
            Role role = new Role(roleName);
            entityManager.persist(role);
            roles.add(role);
        } else {
            roles.addAll(found);
        }
    }
    user.setRoles(roles);
    entityManager.persist(user);
    entityManager.getTransaction().commit();
} finally {
    entityManager.close();
}

就我个人而言，我几乎从不使用JPA的manytomany，我通常将其分解为2个onetomany关系，这样我就有了映射表的一个实体，而映射表是由JPA神奇地创建的。这还为您提供了额外的控制，例如，如果您需要修改或删除用户的角色，您可以直接删除UserRoleMapping实体，而不必在role和user上操作列表。它也给你更多的控制级联。