The custom tags that Struts provides (in the html and logic and bean tag libraries) were a necessary precursor to "out of the box" usage of Struts, in order to make it possible to adopt the basic MVC architectural pattenrs. However, that was *always* a secondary feature in the original vision -- the important part was separation of the view tier logic from the business tier logic.
Craig McClanahan (Original creator of the Struts framework)
As an original historical matter, it would be hubris of the highest variety to question you on this, Craig. As a historical consequence, however, I for one think that this turned out to be the more revolutionary result of struts, leading coding into taglibs in a way not seen before. The controller and MVC (of sorts) pattern in Struts existed in all sorts of forms prior to Struts. Struts did it better than most, maybe better than all the rest, and provided a standard that people could code to. But, those tags were just a big surprise in the way they hit the market. I, for one, now code tags as readily as I code classes. Not as many, of course, but they are a definite weapon in my quiver. A big reason for that is that I could code using Struts taglib code as a learning and doing mechanism together. Blah, blah, blah. This is not meant to be particularly profound. But I did want to give this boost to the tags in Struts. I think they have been very important to Java.
Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
