What problems are you having with components doing navigation? I've
got plenty of component code that navigates e.g.
private void doSort(IRequestCycle cycle) {
Object[] args = cycle.getServiceParameters();
args = Misc.ArraySub(args, 1);
setArgs(args);
String pageName = Gallileo.getListForm(getRealClass());
GenericList l = (GenericList) cycle.getPage(pageName);
l.setArgs(args);
cycle.activate(l);
}
Are you having a different problem and/or is there something
particular about your components that means you can't call cycle.activate()
from within them?
--- Pat
> -----Original Message-----
> From: Kunal Ashar [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 16, 2005 11:01 AM
> To: Tapestry Users
> Subject: Re: Components vs Pages?
>
> There still seems to be a fine line between pages and components.
>
> For example, problems started with when I began developing components
> which needed to take some data from a page/parent component and update
> some data into page/parent component. Intercomponent communication turned
> out to be quite messy, as were components that participated in navigation.
> Apparently pages win where inter communication is needed and where
> navigation is required.
>
> For example, a Login page can be a component if it just indicates that
> user is authenticated but should not be a component if it says, "user is
> authenticated so go to home page". Overall, it seems like components can
> not be used when they will be involved in navigation based on the user
> clicks.
>
> Seems like with Tapestry 3.0, components should be self sustainable. I
> feel component bindings are not matured and may be the reason for some of
> the issues.
>
> Any thoughts?
>
> --
> ___________________________________________________________
> Sign-up for Ads Free at Mail.com
> http://promo.mail.com/adsfreejump.htm
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
