To summarize my question, what if you need to stuff different things into the Request/Session based on things that happen in chains like B_chainEvent and C_chainEvent?
The problem I see is many times you'll be stuck in the middle of a chain cycle and you then need to interact with Request or Session (HTTP). It's this kind of ambigous logic that I find the most frustrating in web apps and I think ends up creating the most headaches for developers. The logic that deals with setting stuff up for display based on certain 'if logic' concerns that need to be looked at. In a pure commons-chain scenario (no Action, no Http tie in?) how are these kinds of things accomplished?
The ActionContext interface defines three maps, requestScope, sessionScope, and applicationScope. We decided that these were logically relevant to any Struts application, regardless of the request/response API. Thus, as long as you're using one ActionContext, you can use these logical maps without being bound to their implementations.
The fact is that the ServletActionContext class uses the HttpServletRequest, its Session, and the initiating Servlet's ApplicationContext to implement these scope maps, but most of your code should be insulated from it.
Does that help? Or did I dodge the real issue?
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
