I'd prefer to put as many logic as possible in the service, component should be like page, for the view tier only, it is easy to test service.
Kai Weber-2 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 > > > -- View this message in context: http://www.nabble.com/Architecture%3A-how-much-logic-should-a-component-contain-tp24183982p24184068.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
