java dto best practices

handle business logic like this, we can deal with BO.POJO (Plain ordinary Java object) simple, rule-free Java objectsJava objects that are purely traditional in meaning. In some object/relation Mapping tools, the Persisent object that maintains database table records is a pure Java object that conforms to the Java Bea

logic like this, we can deal with BO.POJO (Plain ordinary Java object) simple, rule-free Java objectsJava objects that are purely traditional in meaning. In some object/relation Mapping tools, the Persisent object that maintains database table records is a pure Java object that conforms to the Java Bean specification

objectsJava objects that are purely traditional in meaning. In some object/relation Mapping tools, the Persisent object that maintains database table records is a pure Java object that conforms to the Java Bean specification and does not add other properties and methods. My understanding is the most basic Java Bean, only attribute fields and setter and getter Me

this, you can deal with Bo.POJO (POJOs): (Plain old Java Objects), simple Java ObjectThe actual is ordinary JavaBeans, uses the Pojo name is to avoid and the EJB to confuse, and the abbreviation compares directly.Some of these properties and their getter, setter method classes, can sometimes be used as value Object or a DTO (Data Transform object). Of course, it

PO persistent object, data;BO business objects, encapsulated objects, complex objects, which may contain multiple classes;A DTO transmits objects, which are transmitted at the front of the call;VO performance object, front-end interface display.When your business is simple enough, a pojo also looks exactly like Po BO DTO VO, here's an example:For example, there is a user class with only name and phoneFor th

corresponding Po has 100 attributes. However, we only need to display 10 fields on the interface, The client uses Web service to obtain data. It is not necessary to pass the entire Po object to the client, In this case, we can use DTO with only these 10 attributes to pass the results to the client, so that the server table structure will not be exposed. after the client is reached, if this object is used for display on the corresponding interface, th

VO (Value object) value Objects Typically used for data transfer between business tiers, created with the New keyword, collected by GC, is just like a PO that contains only data. But it should be abstracted out of the business object that can correspond to the table, or not, depending on the business needs. Individuals feel like the DTO (data transfer object) is passed on the web. PO (Persistant object) Persistent object The concept of the O/R mappi

more focused on writing data access code.The DAO pattern is one of the standard Java EE design patterns. Developers use this pattern to separate the underlying data access operations from the high-level business logic. A typical DAO implementation has the following several components:1. A DAO factory class;2. a DAO interface;3. A concrete class that implements the DAO interface;4. Data transfer objects (sometimes called value objects).The specific DA

objectsJava objects that are purely traditional in meaning. In some object/relation Mapping tools, the Persisent object that maintains database table records is a pure Java object that conforms to the Java Bean specification and does not add other properties and methods. My understanding is the most basic Java Bean, only attribute fields and setter and getter Me

Java 7: Reading Notes on core technologies and best practices-java source code and byte code operations, java 7 Best Practices General process: developers write the java source code (. java