Hi Howard,
thank you for your reply !
I finally got it. I encapsulated the logic into a service and call it in
the pageValidate for normal pages and in the activateExternalPage for
external pages.
The service is kind of ugly - not the way I wanted to solve my problem.
But hey - it is runnin
If you want to send a client-side redirect, throw a RedirectException.
This is why you see a second request, it how client redirects work.
The user will see the new URL in their browser (as opposed to a
server-side forward, which doesn't cause a second request).
If you need to hold onto some info
Hmmm ... after adding tons of debug-info to my code, I currently found out, why
this behaviour occurs.
ExternalCallback.performCallback(IRequestcycle) is calling activateExternalPage
directly (like mentioned in the docs) - without the chance to do a validation
again (in contrast to the doc of I
Hi Ivano,
thank you for your reply.
I am using Tapestry 4.0.
I need the absolute url, because I want to forward (based on security
constraints of the page (or one of the containing components) currently
rendered) to the right scheme.
Because I noticed, that getRequestCycle() is not the righ
Why do you need to build the url? What Tapestry version are you using?
Ivano Pagano.
Gerald Schöffel wrote:
Hi, it is me again :)
Again with some 'service trouble' ...
An IExternalPage is called from the browser.
in pageValidate (defined in MyBasePage only, all other pages are extending thi
