Article:  |
Wiring Your Web Application with Open Source Java | |
| Subject: | Not a good template for building a domain layer | |
| Date: | 2004-04-28 12:53:42 | |
| From: | gaoy | |
|
Response to: Not a good template for building a domain layer
|
||
|
No DTOs (data transfer objects) are maintained. This may be feasible for certain type of domain models, such as without inheritance and polymorphism. If it is running on a rich client such as Swing or C#, or B2B through web services, I wonder one can avoid using DTOs. Are there frameworks facilitating management of DTOs? Very nice article, and good usage of Spring IoC for decoupling layers via interfaces. |
||
Showing messages 1 through 1 of 1.
-
Not a good template for building a domain layer
2005-01-01 18:18:31 wrschneider99 [View]
Hibernate does indeed let you persist private fields, and this feature can be used to move business rules into the domain layer when appropriate.
Also, I have contributed to an XDoclet module to generate DTOs from metadata in the domain model, called XSnapshot.