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 c
On Wed, Jun 24, 2009 at 9:34 AM, Kai Weber wrote:
> Hi,
Hi!
> what do you think, how much of logic a component should contain?
I completely agree with Peter that no business or data access logic
nor should be in components or pages.
> Say I have a service which retrieves values from somewhere.
e best way to
evolve code into something more decent / reliable and reusable.
Peter
- Original Message -
From: "Kai Weber"
To: "Tapestry users"
Sent: Wednesday, 24 June, 2009 15:34:44 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Architecture: how muc
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 s
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 th
