I think you are on the right track ... however, when doing demos and tutorials I often have a bit of business logic (i.e., Hibernate queries) in my pages, where I can live-reload them. One of my labs is to refactor that into a shared service.
My point is, don't over-engineer early on, do what is convienient and then refactor (mercilessly!) later. On Wed, Jun 24, 2009 at 5:34 AM, Kai Weber <kai.we...@glorybox.de> wrote: > Hi, > > what do you think, how much of logic a component should contain? > > Say I have a service which retrieves values from somewhere. Should I make > this service available in the component or the page containing the component > and setting the values via a @Parameter variable in the component. > > At the moment I see my components more as value providers for my (H)TML > view logic and have all calls to backend services in the pages. But what do > others do and think? > > Regards, Kai > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos
