What about having a UtilityFactory class that provides RequestUtils and ViewUtils? It goes without saying we'd deprecate the static methods and delegate to new, non-static methods on an instance pulled from this factory. Does Struts have a consistent approach to factories and allowing code to replace the factory implementation? I know this would be a good opportunity to put Spring into the mix, but perhaps an abstract factory would be a good first step in abstracting implementation from usage.
My first reaction is that an abstract factory is wasted effort if a Struts API bean is coming soon. I'd be more inclined to have something in the ActionServlet's initialization create and populate a "Struts" with the understanding that how the "Struts" is populated is a moving target. Eventually, I think you and I would agree on a vision which has Spring instantiate the "Struts" and set its "requestUtils" and "viewUtils" properties with implementation classes.
Or are these utils module-scoped?
Unless you're talking about a factory for the "Struts" object itself -- I just wouldn't want to see a proliferation of different factories when the end goal would probably make them obsolete...
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]
