Prioritizing architectures that are easy to unit test outside of a heavy application server. Key Technical Alternatives
Handling "cross-cutting concerns" like transactions and security without cluttering business logic. Expert One-on-One J2EE Development without EJB
Using standard Java objects instead of complex, container-dependent EJBs. Prioritizing architectures that are easy to unit test
The book's central argument is that the J2EE (Java 2 Enterprise Edition) specification had become unnecessarily bloated, often hindering rather than helping developer productivity. Johnson and Hoeller advocated for a shift toward: The book's central argument is that the J2EE
Published in 2004 by Rod Johnson and Juergen Hoeller, is a seminal text that fundamentally reshaped the Java landscape. It famously challenged the "orthodoxy" of the time—specifically the reliance on complex Enterprise JavaBeans (EJB) —and provided the architectural blueprint that led to the creation and dominance of the Spring Framework. Core Philosophy: Simplicity and Productivity
Rather than just critiquing the status quo, the authors provided practical, production-ready alternatives for core enterprise services: J2EE Development Without EJB, Expert One-on-One - Amazon UK
Allowing a container to manage object dependencies, which simplifies testing and decouples code.