Originally posted by Gavin Bong:
Thus entity beans are domain objects ? Although I find that in most of the work that we do; the business logic is in the SLSB layer and the entity beans end up as proprietary POJOs.
Has anyone read Domain Driven Design by Eric Evans ?
Originally posted by Kyle Brown:
In EJB 2.0, yes, CMP Entity beans can be Domain objects. Doesn't happen all the time, but it can work out well at times.
Poorly designed, a controller class will have low cohesion - unfocused and handling too many areas of responsibility; this is called a bloated controller. Signs of bloating include:
1) There is only a single controller class recieving all system events...
2) The controller itself performs many of the tasks necessary to fulfill the system event, without delegating the work. This ususally involves a violation of the Information Expert and High Cohesion
3) A controller has many attributes, and maintains significant information about a system or a domain, which should have been distributed to other objects, or duplicates information found elsewhere.
the entity beans end up as proprietary POJOs.
Originally posted by Ilja Preuss:
Please forgive my ignorance regarding EJBs - but can you shortly explain *when* Entity beans (don't) make good Domain Objects and in which way this is bound to EJB 2.0? Thanks!
I am wondering how Fowler's article differs from Craig Larman's discussion of the bloated controller