Revision as of 13:50, 12 July 2017 edit Urhixidur (talk \| contribs) Administrators 44,826 edits →JavaBeans: dab JSF ← Previous edit		Revision as of 13:50, 12 July 2017 edit undo Urhixidur (talk \| contribs) Administrators 44,826 edits →Transparently adding services: dab AOP Next edit →
Line 59: ===Transparently adding services=== As designs using POJOs have become more commonly used, systems have arisen that give POJOs the full functionality used in frameworks and more choice about which areas of functionality are actually needed. In this model, the programmer creates nothing more than a POJO. This POJO purely focuses on [[business logic]] and has no dependencies on (enterprise) frameworks. [[Aspect-oriented programming~~\|AOP~~]] (AOP) frameworks then transparently add cross-cutting concerns like persistence, transactions, security, and so on.<ref>Martin, Robert C. (2008). Clean Code. Chapter 11, Pure Java AOP Frameworks</ref> [[Spring Framework\|Spring]] was an early implementation of this idea and one of the driving forces behind popularizing this model.

Plain old Java object: Difference between revisions