>ÝThis also installs the "split" between the "process-action" andÝ"process-view" sub-chains, although I haven't yet changed the ÝSelectInput command to return "false" to eliminate the need for Ýlater commands to check to see if the form was valid.
ÝI think the big outstanding question in my mind now is what kind of Ýcontext we want to pass into the "process-view" subchain. ÝIn some Ýearlier discussions, there was talk about a "ViewContext" -- I Ýhaven't touched that at all, but I'm whether it's worth Ýdistinguishing that from the ActionContext. Ý
The idea behind the ViewContext is that it is a specialized facade designed to tell the tags (or other tools) what they need to know, the way they want to know it.
It would also be some thing that would be easy to mock, for testing tag and tool code in isolation.
I'll start working up an API based on what teams like the Velocity Tools crew designed. If we do need one, it would probably use the ActionContext via composition.
Perhaps I should wait a bit to wipe out the WrappingLookupCommand and ContextBase, then.
ÝI was >Ýalso wondering whether we ought to routinely put the context intoÝthe request scope so that that object is available to view Ýtechnologies like JSPs and Velocity templates. ÝIt seems like it Ýwould be handy.
The last sentence is the use-case for a ViewContext.
The use-case is not within the RequestProcessor but without. The ViewContext is the specific API we want to expose to the presentation layer, as opposed to the control layer. So, the ViewContext has no semanticas in regard to navigation and may have additional semantics in regard to rendering. Following the well-worn Velocity philosophy, we want the ViewContext to be read-only, free of HTTP and navigational semantics, and easy to mock for testing view tools (and only view tools).
What you see is what you want :)
OK; technically the ContextBase exposes the base context, so we'd have to decide if the ease of not copying or proxying for each specific property outweighs the risk of exposing that for those who want to play with fire.
Thanks for weighing in!
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]
