In the previous chapter, we discussed session-scoped stateful Seam components. In most web frameworks, the application state is completely managed in the
HttpSession object, so the session scope is the only stateful scope. However, for most applications, the session scope is too coarsely grained for effective state management. We already covered most of the reasons in Chapter 6. Let’s quickly recap the key points here:
• To manage complex application state in an HTTP session, you must write a lot of code to manually shuffle objects into and out of the session. If you forget to save a modified state object back into the session, the application will exhibit hard-to-debug behavior errors at runtime.
• A single timeout ...