In the previous section, we saw how it's possible to store, or cache, data by using simple Servlets. We looked at three different types of data scopes that can easily be used, local variables, HTTP session scope, and global variables.
However, Seam provides a more elegant solution that allows us to specify the scope of Seam components.
The scope of a component specifies how long the component will live, that is, how long the component is effectively cached in memory and available to the developer before it is removed from memory and is no longer available.
Within Seam, there are seven different scope contexts that can be applied to any Seam component. Ranging from the shortest scope context to the longest, these scope contexts are:
Stateless
Event
Page
Conversation
Session
Business Process
Application
Although we have defined the Business Process as having a shorter scope context than the Application scope, it is possible that Business Processes can last longer than Application...