DTO、DAO和实体？是否需要实体？和那3个最好的Pratic？

Question

public interface CustomerResource {

    @GET
    @Path("/getCustomerListByUserID/{userID}")
    Response getCustomerListByUserID(@PathParam("userID") String userID);

    @DELETE
    @Path("/deleteCustomer/{customerID}")
    Response deleteCustomer(@PathParam("customerID") int customerID);

    @POST
    @Path("/updateCustomer")
    Response updateCustomer(CustomerDTO customer);
 }

public class CustomerResourceImpl implements CustomerResource{

 @Override
 public Response deleteCustomer(int customerID) {
     internalService.deleteCustomer(customerID);
 }

 @Override
 public Response getCustomerListByUserID(String userID) {
     internalService.getCustomerListByUserID(customerID);
 }

 @Override
 public Response updateCustomer(CustomerDTO customer) {
     internalService.updateCustomer(customer);
 }
}

public interface CustomerDAO extends BaseDAO<CustomerDTO> {
 
     List<CustomerDTO> getCustomerListByUserID(String userID);
 
     void deleteCustomer(Integer customerID);
 
     void updateCustomer(CustomerDTO customer);
 }

太感谢你们了！祝大家成功！

Answer 1

DTO是Data Transfer Object的缩写，因此它用于在应用程序的类和模块之间传输数据。

DTO应该只包含数据、getter、setter和构造函数的私有字段。不建议DTO将业务逻辑方法添加到此类类中，但添加一些util方法是可以的。DAO是Data Access Object的缩写，因此它应该封装在数据存储（数据库、文件系统等）中检索、保存和更新数据的逻辑。

下面是DAO和DTO接口的示例：

interface PersonDTO {
    String getName();
    void setName(String name);
    //.....
}

interface PersonDAO {
    PersonDTO findById(long id);
    void save(PersonDTO person);
    //.....
}

@Entity
public class Person {
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
private Long id;
@NotNull
protected String name;
...getter and setter
}