On Tue, Nov 23, 2010 at 5:09 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote:
> On Tue, 23 Nov 2010 02:45:49 -0200, Taha Hafeez <tawus.tapes...@gmail.com> > wrote: > > Hi, >> > > Hi! > > Correct me if i am wrong but wicket and tapestry are based on different >> philosophies. Tapestry IOC is the recognition by tapestry that there are >> certain services that are presentation services and require an exclusive >> support in the presentation layer. >> > > I don't know what you mean by presentation service and exclusive support. > All Tapestry-the-web-framework services are ordinary Tapestry-IoC services, > not being treated differently than any other. > > Excuse my English but I used this term to separate services pertaining to presentation layer (That is what you also say in the next line)... A number of frameworks don't see the need of these services as they implement these in other ways. 'Exclusive' as tapestry has its own IOC. > You don't think of using IoC inside a Web framework until you see it and > then you realize how good the idea is. Just take a look at how easy is to > override almost anything in Tapestry. ;) > > > I absolutely agree but as I said Wicket has a different philosophy which also means there are people who don't agree with it. I do and that is why I am opting for it but there are people who prefer other ways :) > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > regards Taha
