In the previous chapter, we discussed session-scoped Seam stateful components. In most web frameworks, the application state is completely managed in the
HttpSession object and, hence, session scope is the only stateful scope. However, for most applications, the session scope is also too coarsely grained for effective state management. We already covered most of the reasons in Chapter 5, An Introduction to Stateful Framework. Let’s quickly recap the key points here:
- To manage complex application state in an HTTP session, you must write a lot of code yourself 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 ...