Data transfer object (DTO) is an object that carries data between processes. The motivation for its use has to do with the fact that communication between processes is usually done resorting to remote interfaces (e.g. web services), where each call is an expensive operation.
0
votes
1answer
139 views
Map a hierarchy of nested DTO objects to a list of business objects [closed]
Consider I download my data into this data structures:
...
0
votes
1answer
2k views
Mapping interface between POJOs and DTOs
Following up on this question DTO interfaces for implementing web service integration I came up with this implementation.
Data Transfer Object interface following a java.util.Map protocol. The ...
3
votes
1answer
1k views
DTO interfaces for implementing web service integration
I am trying to define some interfaces to implement some web service integration middleware.
The SOA pattern that fits this system is probably the Multi-Channel Endpoint.
I expect a lot of mapping of ...
2
votes
1answer
203 views
Passing a DTO into a static domain 'Create' method
I'm wondering if it's bad practice to couple my DTO to my domain object like this and pass the object itself into Create(). Is it better to just give the parameters ...
6
votes
1answer
399 views
Implementing a domain model
My domain model consists mostly of simple DTOs, i.e. 'Data Transfer Objects' which this article distinguishes from 'Plain Old C# Objects', like this one:
...
4
votes
1answer
110 views
Is the “current connected user” an information that should be shared with the domain?
I'm working right now in a readers social network. The main points are this:
When an user connects with his account I save his user id in the
session variable.
My MVC is working with DTO's all the ...
