On Fri, Sep 11, 2009 at 7:26 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > Em Fri, 11 Sep 2009 23:11:59 -0300, Kalle Korhonen > <kalle.o.korho...@gmail.com> escreveu: > I think onValidate() is for validation, the data store should only be > changed (or attepted to be changed) when validation succeeds and controller > classes (business rules tier) should deal with transactions, not > Tapestry-related code (nor any UI code). I write code following the > three-tiers architecture and the separation of concerns philosphy strictly.
Ok I see where you are coming from. I'm not a purist - I typically do the least amount of work up front and try to avoid the extra layer of indirection whenever possible. Tapestry offers a fairly clean separation of logic and UI concerns straight-up and unless I need a separate business layer (say if I had a completely different interface to the same data), I don't add it in automatically. But I totally understand your point of view - it's more in line of JEE/EJB architecture and offers its own benefits. Kalle --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
