I have a question that I could never solve:
Given these two architectures
the first
UI layer
|
Application layer
|
Domain Layer
|
Infrastructure Layer
second
Client Tiers
|
Presentation Tiers
|
Business Tiers
|
Integration Tiers
|
Resources Tiers
What is the difference between the two.
Where the essence of beans lies in this architecture. If I have a business layer with an object that implements business logic, why would I add behavior to entity beans. I read somewhere that this is an anti-pattern for model object objects without behavior.
thank
Update
This is actually a project (training) that I need to do to get my msc in distributed systems.
These are actually the technologies that I use
Struts 2 JPA HSQLDB
So, if I understand well
My application consists of
Client level (web browser) Presentation level (Rack 2) Business level (POJO + JPA) Integration level (with hibernate DAOs) Resource level (HSQLDB)
, (tomact), . ?
JPA, , :
dao JPA.
bean (, EJB), -. beahvior JPA.
, , . CatalogueManager, , . EmployeeManager, . , , PurchaseRequestManager, - PurchaseRequest.
, , - , PurchaseManager JPA PurchaseRequest, EmployeeManager = > , Employee JPA.
, , . JPA . ?