Its very common yet you couldn't give a straight answer!
I AM bothered because I'd want some convention on where to put logic
(actually, controller logic NOT biz logic), or at least a rule of
thumb that everyone on a team should follow. I wouldn't want one guy
to do something one way and another guy doing it another way...
On 5/8/05, Kent Tong <[EMAIL PROTECTED]> wrote:
> Yves Sy <yves.sy <at> gmail.com> writes:
>
> > Well of course for getting input you use (1), but I've seen samples
> > even in the Tapestry in Action book where it goes like:
> >
> > public void myLinkCliked(IRequestCycle cycle) {
> > NextPage n = (NextPage) cycle.getPage("nextPage");
> > n.showNextPage(cycle);
> > }
> >
> > ..which uses (2).
> >
> > Of course the code in n.showNextPage() could easily be in
> > myLinkClicked() and would work the same...
>
> That really depends what showNextPage() does and is a question
> of where the logic should reside. However, I wouldn't bother
> much as this issue is very cmomon in our daily programming
> life (which class to put this method?).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
A bus station is where a bus stops. A train station is where a train
stops. On my desk I have a work station...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
