Java Reference
In-Depth Information
of the use case. The classes and components you created in
the class and component diagram should be represented,
along with the calls between them necessary to implement the
use case being documented.
Design Decisions
This section provides highlights on the various design
decisions an architect has to make while building the
enterprise Java solutions. This section covers all the critical
areas including, transaction, security, frameworks, hardware
sizing, deployment models and scaling of the applications.
Java EE Frameworks for Rescue
The common practice in J2EE 1.3 and J2EE 1.4 was indeed to
supplement the J2EE stack with quite a lot of additional
frameworks.
Starting from Java EE 5 and now certainly with Java EE 6 &
7 you don't need additional frameworks as JEE provides
reference implementations for all the specs. Everything core
Spring container provided to J2EE can now be done with the
lightweight EJB3.1 and CDI component models, ORM
support is provided by JPA which is often implemented by
Hibernate. The MVC web framework is part of the standard
stack via JSF.
Of course individuals may still prefer the Spring and Struts
programming APIs, but with Java EE 6 there is no pressing
need to use them. Or put differently, it's no longer absolutely
needed
to
complement
Java
EE
unless
if
there
aren't
