So the answer is: No Tapestry does not support that case out of the box yet.
http://tapestry.apache.org/tapestry5/tapestry-core/guide/pagenav.html
You can see there how Tapestry handles different return types, and it
doesn't list what you are talking about. Myself, I like to call it
server-side redirect; and it was Tapestry's default behavior before T5.
The new way is nice for various reasons, but in edge cases I do miss
having the option of the old way.
First step is to create a JIRA issue to track what you want.
Second, someone will have to take the time to try to hack together a
code solution. Might actually be relatively easy, but I don't have the
code in front of me right now.
Christian Gorbach wrote:
it's indeed a redirect. so it seems no real serverside page delegation is
possible without custom contributions.
Stephan Schwab wrote:
Christian Gorbach wrote:
is it possible to implement a dispatcher/delegate page which is able to
forward to another known page class if business logic decides to do so.
It should be a pure server-side RequestDispatcher.forward and no
redirect.
You can return a page from the onActivate() method. But I think that will
be a redirect.
Stephan
--
http://www.stephan-schwab.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
