Chapter 1. Seam unifies Java EE
Figure 1.1. The great framework decision
Figure 1.2. A cross section of the technologies incorporated in the Seam stack
Figure 1.3. Seam’s stack matrix, with options for a state and persistence provider
Figure 1.4. Seam cuts down on superfluous XML configuration that’s difficult to keep in sync with the source code.
Figure 1.5. Interceptors trap method calls and perform cross-cutting logic around a method invocation.
Figure 1.6. The golf tips page, which renders the collection of tips at the top and a form for contributing a new tip at the bottom
Figure 1.7. Seam cuts out the middleman by eliminating the need for a JSF backing bean. Instead, the entity class and the EJB 3.0 session bean work together to capture data from the UI and handle the event to persist the data.
Figure 1.8. The lifetimes of the six scopes in a Seam application. The standard scopes are represented by dashed lines. The scopes that Seam contributes appear as solid lines. The business process scope is persisted to a database and can thus outlive the application scope across server restarts.
Figure 1.9. Using the extended persistence context to keep an object in scope for an entire use case, even across multiple page views. The extended persistence context avoids the need to merge detached entity instances.
Chapter 2. Putting seam-gen to work
Figure 2.1. Reverse engineering entity classes from an existing database schema, termed bottom-up development