You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by The Chris Method <th...@gmail.com> on 2005/08/03 15:04:51 UTC
Re: activeExternalPage parameters
Anyone?
On 7/28/05, The Chris Method <th...@gmail.com> wrote:
>
> This may be an obvious question, or maybe I just don't understand design
> too well, but...
> Why does the activateExternalPage method take both an Object[] of
> parameters and an IRequestCycle, which contains said Object[] anyway?
>
> I've been using Tapestry for some time now (two years), and have had this
> question in the back of my mind for a while. When I first thought about it,
> I didn't look into the internals too much, and just always used the Object[]
> to get parameters, thinking they were somehow different, maybe processed in
> some way, something. After looking at the code, though, I see that that is
> not the case. The external service does this:
>
> Object[] parameters = getParameters(cycle);
> cycle.setServiceParameters(parameters);
> cycle.activate(page);
> page.activateExternalPage(parameters, cycle);
>
> Is this just a design thing? Or am I missing something?
>