I'm continuing to plug away on elaborating an ActionContext interface and a ServletActionContext implementation. I'm generally happy with how it's coming, but it's fairly time-consuming, so again, there's a chance to solicit feedback, and also an interest in getting the feedback *before* I do a bunch of stuff which people want undone...

Anyway, in going along and adjusting the base commands to use ActionContext with typesafe property methods, I'm having mild second thoughts about the direct references to WebContext in those commands. My ContextWrapper approach makes it relatively straightforward to add a "WebActionContext" class in between ActionContextBase and ServletActionContext, but I'm not sure if I feel like it's as Abstract as all that to have dependencies on even the "WebContext" interface.

Then again, the WebContext interface is fairly innocuous. Perhaps it makes sense to actually implicitly adopt it as part of the ActionContext API.

http://jakarta.apache.org/commons/chain/apidocs/org/apache/commons/chain/web/WebContext.html

Something to chew on until I get back to working on the conversion.

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