Thx for the reply. I was kindof expecting that. I have a large collection of lots of different Objects of varying classes (all stemming from the one superclass) and have a view/edit page for each of them. Instead of a big switch I simply wanted to redirect to page "viewthe"+selectedType and then pass the ID;
I know its not ideal but it felt like a quick way of achieving what I required. Any other recommendations? On a page I have rows (one per object) that all stem from one superclass. On selection of a particular row I want to redirect to the appropriate viewer page. There will be at least 20 different subclasses (nesting no more than 2) If required I can do a big switch but it rather find a smarter way to redirect to the right page and pass in the ID of the particular object. A -----Original Message----- From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] Sent: 18 January 2010 13:07 To: Tapestry users Subject: Re: Passing Activation parameters to a page On Mon, 18 Jan 2010 11:00:12 -0200, <aidan.oha...@bt.com> wrote: > Hi folks, Hi! > But I have a situation where I need to use the String method for page > navigation but still need to pass a parameter. You can't return a String and still pass the activation context. Why do you need to return a String at first? -- Thiago H. de Paula Figueiredo Coordenador e professor da Especialização em Engenharia de Software com Ênfase em Java da Faculdade Pitágoras Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate Sócio, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
