edgar writes: >Unfortunately, an innordinately large percentage of development >time is spent with the tag library, as even a casual perusal >of this list reveals.
I think that's mostly about not understanding how to develop with tags, especially in a Model 2 architecture. It's a very different approach than developing an app with Model 1 and scriplets. Much of the problem, I think, is that people try to put old wine into new bottles. I did some work in Cold Fusion before Struts, so the tag and tool approaches seemed quite natural to me. I've also written applications in so many environments now, that I've long started to see the database as one thing and the presentation as another. So Model 2 came naturally tool. IMHO, what helps the most is drawing a firmer contrast between the Struts Core and the rest of the presentation layer. The Struts tags are one example of how to expose the Struts framework core to the presentation page. Struts-el, stxx, the Velocity View tools, and the (upcoming) struts-faces, are other ways of exposing the core framework components to the presentation page. Properly designed, you should be able to use your Struts controller with any these presentation layers. Where I think people run into problems is that they try to do controller things in the presentation page and presentation things in the controller. Like Vic said, if you are having trouble doing some thing "with" the tags, it's usually because you are doing too little with the controller. In a MVC/Model 2 application, the presentation page should be a glorified mail merge job. It shouldn't "do" anything but output what the controller has given it to output. In the future, there will be more Struts appplication using even more presentation layers, the Struts tags, the EL tags, the JSF tags, the Velocity View tools, XLST, Jelly, and whatever else we think of next =:0) But behind all this chrome, there can still be the same core framework holding all the pieces together. -Ted. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
