Thanks Kris, you made me think - I don't need to use doSomething method at this 
point - so a pagelink was enough and I could control that from the tml. 

Yours and Thiago's suggestions were excellent - ill try both out and see which 
one I understand best ;)
A


-----Original Message-----
From: Kristian Marinkovic [mailto:kristian.marinko...@porsche.co.at] 
Sent: 18 January 2010 13:12
To: Tapestry users
Subject: Antwort: Passing Activation parameters to a page

hi, 

you can't do it this way. if you return a string Tapestry will interpret it as 
a logical page name and return the rendered page as response (see 
PageNameComponentEventResultProcessor)

but you can create a Link with the desired paramters using the 
LinkSoruce.createPageRenderLink method and return it in your action method

g,
kris



<aidan.oha...@bt.com>
18.01.2010 14:00
Bitte antworten an
"Tapestry users" <users@tapestry.apache.org>


An
<users@tapestry.apache.org>
Kopie

Thema
Passing Activation parameters to a page







Hi folks,
Quick question - I am trying to pass parameters using the activation 
context.
I normally use:
InjectPage
PageX thePage
...
...
onSomeEvent() {
thePage.setSomeParameter("SS");
Return thePage;
}

But I have a situation where I need to use the String method for page 
navigation but still need to pass a parameter. 

onSomeEvent(){ 
return "PageX"; }

Any advice on how I pass activation parameters to PageX when using this 
method?
Cant find anything relevant on Nabble.  Hope you can help.
Aidan

-----Original Message-----
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] 
Sent: 17 January 2010 18:25
To: Tapestry users
Subject: Re: Different ExceptionReport for different pages

On Sun, 17 Jan 2010 15:41:08 -0200, Richard Hill <r...@su3analytics.com>
wrote:

> Hi All,

Hi!

> I have an ExceptionReport.java, .tml to present a pretty error page to 
> users. However there is one page where I would like to have a 
> different exception page. Is this possible?

Simple answer: you can, but I think it's not worth the hassle. Just use 
some logic in your error page to show different content to different 
exceptions. You can also redirect to another page in your ExceptionReport 
page.

Sophisticated answer: override the RequestExceptionHandler service. Draw 
some inspiration from RequestExceptionHandlerImpl.

--
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



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to