"coming soon"? Is that an offer? :)
uh-oh. Well, to be honest, not very soon, as I'm going to be mostly offline for the next week for the holidays. (I did say "*if*...)
I haven't felt like there's a clear consensus on how to move such a thing forward, and I guess I'm still in "ask permission" mode instead of "ask forgiveness" mode. I'm not really even sure how to move it forward in small measured steps to get people looking at something concrete for reactions.
I like the API bean aka ViewContext aka ConfigHelper and agree it is a better solution. Reading over the API bean thread, Ted has convinced me this bean would actually be created for each request probably somewhere early in the chain. While it could be passed around via the Context, I'd vote to also store it in ThreadLocal so we could call ViewContext.getCurrentInstance() at any point.
Now, when I said API bean, I meant something representing the most global level of Struts. It would be the thing which would encapsulate most things which are now in the ServletContext.
Assuming we'd have a CreateViewContext chain command, would we pass in the class names to instantiate for RequestUtils and ViewUtils as command attributes in the config? This would allow the util implementation to not only be module scoped but request scoped if desired since the user can have complete control over the chains.
This seems as though it would work, and is probably a good way to take a small step forward without requiring too much debate.
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]
