On Sat, 26 Jul 2003, David Graham wrote:
> Date: Sat, 26 Jul 2003 11:32:57 -0700 (PDT) > From: David Graham <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: New TagUtils class > > Yesterday I committed a new TagUtils class for all tag related methods > from RequestUtils to be moved into. Rob has helped out with the movement > and wrote this in one message: > > "Overall we may need a glue class, instead of calling this a tagutil since > other display technologies other than JSP might be able to make use of > this library." > > I considered naming the class JspUtils or ViewUtils but chose TagUtils > because I didn't think it would be called from a JSP and other view > technologies wouldn't necessarily need these methods. What does everyone > think about this? Now is the time to change the name before 1.2 comes > out. > So far, it looks like all of the APIs we are migrating require JSP APIs (for things like PageContext), so ViewUtils might be a little too broad. I mildly favor JspUtils over TagUtils, because view technologies that use JSP but not our existing tags -- everything from JSTL's XML tags to JavaServer Faces component tags -- will still find these methods useful. This naming would also let us decide to formally support any other view technology we chose to with a FooUtils adapter class that exposes Struts concepts to that view technology. (And, when we refactor the build process, we can make the compilation of these adapters conditional on whether the corresponding view technology API classes are available.) > Thanks, > David Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
