On Tue, Nov 23, 2010 at 5:16 PM, Christian Riedel <cr.ml...@googlemail.com>wrote:
> It's just a pitty that you can't override so much so easily in Wicket :) > Yes, I agree but then it is not a problem of Wicket it is more of an advantage of IOC over inheritance. regards Taha > > Am 23.11.2010 um 12:39 schrieb Thiago H. de Paula Figueiredo: > > > 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. > > > > 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. ;) > > > > -- > > 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 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
