ecb-pattern

问题 I'm not sure if i got the right concept. I was told by people that Boundary = View Entity = Model Control = Controller however based on my knowledge of MVC. (fat model, thin controller) Isn't the Boundary = Controller, Control = Model (the busienss logic) and Entity = Model (The orm classes or similar entity classes which does only crud ). I may be wrong, please guide me! 回答1: Actually your first definition is simply correct. The meaning of words is sometimes confusing. The following link

问题 I'm not sure if i got the right concept. I was told by people that Boundary = View Entity = Model Control = Controller however based on my knowledge of MVC. (fat model, thin controller) Isn't the Boundary = Controller, Control = Model (the busienss logic) and Entity = Model (The orm classes or similar entity classes which does only crud ). I may be wrong, please guide me! 回答1: Actually your first definition is simply correct. The meaning of words is sometimes confusing. The following link

问题 Premise I've recently read/watched a lot of articles/videos by Java Champion Adam Bien, where he advocates the usage of the ancient but renewed Entity - Control - Boundary Design Pattern JAVA EE >= 6. Leveraging on CDI, EJB 3.1, JPA 2 and other JAVA EE 6 features, this pattern should help creating more business-oriented components , easier to unit-test, and with a higher separation of concerns based on the responsibilities. Since I'm using all of the features listed above, and this pattern