EJB 2 backward compatibility). Figure 1.4 shows how the Web Profile compares with the
complete Java EE platform.
Figure 1.4. Java EE Web Profile versus full Java EE platform
The Web Profile defines a complete stack on which to build a modern web application.
Web applications are now rarely written from the ground up using raw Servlets, but instead
sit on top of JSF and make use of the various EE technologies.
1.4.2. EJB Lite
Similar to the idea of the Java EE 7 Web Profile, EJB 3.2 also comes in a scaled-down,
lighter-weight version called EJB 3.2 Lite. EJB Lite goes hand-in-hand with the Web Pro-
file and is intended for web applications. Just as with the Web Profile, any vendor imple-
menting the EJB 3.2 Lite API is free to include EJB features as they wish. From a practical
standpoint, the most important thing that EJB 3.2 Lite does is remove support for EJB 2
backward compatibility. This means that an EJB container can be much more lightweight
because it doesn't have to implement the old APIs in addition to the lightweight EJB 3
model. Because EJB 3.2 Lite also doesn't include support for MDBs and remoting, it can
mean a lighter-weight server if you don't need these features. For reference, table 1.2 com-
pares the major EJB and EJB Lite features.