If the component needs 2 string parameters to function, then it needs 2 string parameters! (Much like if a method needs 2 strings, then you need to pass 2 strings.)
Other alternatives are dependent on re-usability requirements: a) If the 2 strings are always used together then wrap them in a value object and pass that (you can pass anything as Component parameters). b) If the component is deeply nested and / or the strings need to be available to multiple components (and you're certain they'll always exist) then you could push them on the Environmental stack and not pass any parameters - just have the component query the stack. Steve. -- Steve Eynon On 24 August 2011 18:07, Borut Bolčina <borut.bolc...@gmail.com> wrote: > Hi, > > if a component needs to have its parent's activation context (say two > strings), is the preffered way to pass it as parameters or is there a "less > code way"? > > The solution must not use a session. > > Cheers, > Borut > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
