Why do you want to avoid this?
If you're going to be using the previous page in your new page (for
example, to provide a link back to it) then you need a reference to it.
You may as well pass this in the constructor.
Alastair
Paolo Di Tommaso wrote:
Yes, but I would to avoid this, basically I'm looking for a way to discover
dinamically the calling wicket page instance (if exists ..)
Thanks, Paolo
On 8/3/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote:
you could have a constructor B(Page referrer)
and pass the referrer page as a parameter like:
this.setResponsePage(new B(this));
hth,
gerolf
On 8/3/07, Paolo Di Tommaso <[EMAIL PROTECTED]> wrote:
Dear Wicket gurus,
Suppose I have two Wicket page, let's say page A and B,
with the following simple navigation rule A --> B using something like
A. setResponsePage( new B() )
At compiles time A know B , but B does not know A.
It there a way to get - at runtime - from page B the reference to caller
A
page instance?
Basically I'm trying to implement something like the HTTP referer
mechanism.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
