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...
I'm a bit concerned about this because I've already seen some code in
a project where it got quite inconsistent (using both 1 and 2) and I
found it messy.
On 5/6/05, Kent Tong <[EMAIL PROTECTED]> wrote:
> Yves Sy <yves.sy <at> gmail.com> writes:
>
> > 1. Handle the calls to service layer on the current page and just
> > activate the next page at the end of the listener method;
> > 2. Get the next page and pass execution (and the cycle) to that next
> > page by calling a method from that page right away...
>
> (1), otherwise how can you get the user input?
>
> ---------------------------------------------------------------------
> 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]
