OK: the ComposableRequestProcessor now makes sure that the context passed to the initial chain command is an instance of ActionContext -- this feels like a much stronger model than the wrapping process. I will probably completely remove the WrappingLookupCommand and ContextWrapper classes from SVN. If anyone interested in chain thinks its worthwhile, maybe I'll move them to commons-chain; otherwise, I'll let them sit until it seems more relevant.

There's still a historic link to ServletWebContext in the ServletActionContext, but it seems gratuitous now that the ServletActionContext isn't primarily used as a wrapper; I will probably take that out soon.

I believe now that we have a decent grounding to begin using the ActionContext as the request-scoped parameter throughout Struts - I think it can be applied to ActionForm and Action to hide dependencies on the Servlet API (and in ActionForm, to finally deprecate ActionErrors!)

Are there any reasons not to press ahead with changes like that?

Beyond looking at further uses for ActionContext, I also want to start thinking about a Struts API bean which might do for the application what ActionContext does for the request.

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]



Reply via email to