Article:  |
Wiring Your Web Application with Open Source Java | |
| Subject: | Not a good template for building a domain layer | |
| Date: | 2004-04-13 12:15:45 | |
| From: | while(true) | |
|
Response to: Not a good template for building a domain layer
|
||
|
By putting your business logic in your service layer, as opposed to your domain layer, you miss out on all the important benefits of OO for your business layer, and end up back in the procedural world. "all the important benefits of OO" We are missing all of them. I'm not really seeing this. I read Martin's article and I'm still not really seeing what benefits I'm missing by having a service layer.
|
||
Showing messages 1 through 1 of 1.
-
Not a good template for building a domain layer
2004-04-13 12:31:34 Groo [View]
In a simple example such as this it may not be as obvious, but as you get a more complex domain model it becomes more apparent. For example, even something as trivial as polymorphism is hard to take advantage of without a proper domain model.