dto

现在项目中要求用mapstruct 每个接口要有自己的接收参数对象，就是controller层的入参对象，以Req结尾，比如：IndicatorReq 规定service层不能直接用IndicatorReq，要转换为IndicatorDTO service返回结果也是DTO结尾，比如IndicatorResultDTO 在controller层返回不能直接用IndicatorResultDTO，要转换为IndicatorResultResp 所有一般有四个对象：IndicatorReq -> IndicatorDTO、IndicatorResultDTO -> IndicatorResultResp 在controller层转换 1.引入mapstruct依赖 2.下载插件，idea有对应的mapstruct版本,不对应报错 3.代码： controller层 public List<SelectDimensionResp> getEachDimension (IndicatorReq indicatorReq){ //req 转DTO IndicatorDTO indicatorDTO = RegulationTransfer.INSTANCE.toSelectDimensionDTO(indicatoReq); //DTO作为参数传入service层 List

ContentType --> EF model ContentTypes --> DTO In my OData controller: public Task<IQueryable<ContentTypes>> Get(ODataQueryOptions<ContentTypes> options) { var result = options.ApplyTo(_repository.Query().Get() .Where(u => u.UserId == userId) .OrderBy(o => o.Description)) .Cast<ContentTypes>(); return result; } I get an error 500 when trying to apply the ODataQueryOptions . Since the class already inherits ODataController do I even need to do the options.ApplyTo(...) ? The solution for this was to ensure the return type is the the DTO's type, and that the ODataQueryOptions are applied to the EF

Closed . This question is opinion-based . It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . Closed 2 years ago . I'm designing a Web API with the usual CRUD operations on a Person entity. The problem is that I don't know how to design the DTOs. The entity is as follows: public class Person { public int Id { get; set; } public string Name { get; set; } public int Age { get; set; } } I have determined that the DTO should have the very same members: public class PersonDto { public int Id

We're building an n-tier system based on WCF (but not Entity Framework) and we've run into a discussion of the best way to implement updates of large entities. We've created DTOs and map data from our domain model into theese when data is sent to the client. The client then makes some changes and sends them back using the same DTO, in our current implementation. Some of our entities might have 80-100 properties, but perhaps the client only makes changes to one or a few of them. It seems inefficient to populate the whole DTO and send it back and then try to figure out on the server side wich

请求方式： （1）后台API：HttpPost [FromForm] UserRetisterDTO dto 前端请求： { 　　body:qs.stringify(dto), 　headers:{ 　　Accept: 'application/json', 　　'Content-Type': 'application/x-www-form-urlencoded;charset=UTF-8', 　　 } } （2）后台API：HttpPost UserRetisterDTO dto 前端请求： { 　　 　　data: dto, 　headers: { 　　Accept: '*/*', 　　'Content-Type': 'application/json', 　　} } 来源： https://www.cnblogs.com/blog-zhaof/p/11987785.html