[英]Is there an advantage to having individual endpoints over a single endpoint with a path variable?
[英]How to creating a single endpoint with multiple endpoints connecting to it
我正在嘗試創建下表以在用戶注冊時獲取用戶信息。
根據我在互聯網上閱讀的教程,我需要創建四個實體類,分別是USER,USER_DETAILS,ROLE和USER_ROLE。 但是我的問題是,當我想在應用程序中創建用戶時,我是否必須具有4種不同的發布方法,或者有一種方法可以一次將用戶數據添加到相關表中。
我希望能夠將數據發布到單個url,並在用戶提供所有詳細信息時立即填充所有帶有外鍵的表。
就像是 :
{
"userName": “ME",
"password": "1234”,
“DOB": “1988-05-12",
"email": “test@test.org",
“role": “admin",
"country": "Ireland",
"registrationLocation": "Dublin",
"timeStamp": "18-01-2018T12:23:08"
}
將其發布到單個網址,例如:localhost:8080 / live / api
這是我的代碼:
用戶詳細信息
public class UserDetails {
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
private long id;
private Users user;
@NotBlank
private String DOB;
public UserDetails() {
}
public UserDetails( String DOB) {
this. DOB = DOB;
}
public String getDOB() {
return DOB;
}
public void setTitle(String DOB) {
DOB = DOB;
}
@OneToOne(cascade = CascadeType.ALL)
@JoinColumn(name = "userID")
public Users getUser() {
return user;
}
用戶
@Entity
@Table(name = "Users",
uniqueConstraints =
{
@UniqueConstraint(columnNames = "email"),
@UniqueConstraint(columnNames = "username")
}
)
public class Users implements Serializable {
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
private long userID;
@NotBlank
@Size(min = 5, max = 100, message = "Please enter between 8 and 100 characters.")
private String password;
@NotBlank
private String username;
private Role role;
public Users() {
}
public Users(long userID, String password, String username, Role role) {
this.userID = userID;
this.password = password;
this.username = username;
this.role = role;
}
@OneToMany(cascade = CascadeType.ALL)
@JoinColumn(name = "roleID")
public Role getRoles() {
return role;
}
public long getUserID() {
return userID;
}
public void setUserID(long userID) {
this.userID = userID;
}
public String getPassword() {
return password;
}
public void setPassword(String password) {
this.password = password;
}
public String getUsername() {
return username;
}
public void setUsername(String username) {
this.username = username;
}
public Role getRole() {
return role;
}
public void setRole(Role role) {
this.role = role;
}
}
用戶角色
@Entity
public class UserRole implements Serializable {
private Role role;
private Users user;
public UserRole() {
}
public UserRole(Role role, Users user) {
this.role = role;
this.user = user;
}
public Role getRole() {
return role;
}
public void setRole(Role role) {
this.role = role;
}
public Users getUser() {
return user;
}
public void setUser(Users user) {
this.user = user;
}
}
控制器類方法
@RequestMapping(method = RequestMethod.POST, value = "/api/usermanagement/users")
public Response createUser(@Valid @RequestBody Users user){
return userService.AddUser(user);
}
您可以像給出示例一樣將所有相關信息發布到1個端點,然后從UserService類(最好是Impl類)中,可以調用所有相關方法以保存相關詳細信息。 例如,
@Service
public class UserServiceImpl implements UserService {
public Response addUser(Users user){
//get details from Users and populate to entities User and UserDetails.
// Save User and UserDetails. Return Response
}
}
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.