IMO, many of the problems discussed in that article are solved with tag libraries and the MVC model. I think the real problems with this approach, servlet(s) as controller(s) and JSPs as views, are complexity and a real code reuse.
David > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:tapestry- > [EMAIL PROTECTED]] On Behalf Of Geoff Longman > Sent: Tuesday, August 13, 2002 3:52 PM > To: [EMAIL PROTECTED] > Subject: [Tapestry-developer] A handy link for... > > ...to give out when someone asks why Tapestry is better than JSP > > http://www.servlets.com/soapbox/problems-jsp.html > > Geoff > > > Geoffrey Longman > Intelligent Works Inc. > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Dice - The leading online job board > for high-tech professionals. Search and apply for tech jobs today! > http://seeker.dice.com/seeker.epl?rel_code=31 > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
