If you don't want that then you could add a link itself to the compont hierarchy (so give the link a wicket:id )

Then in the onClick of the link you can give yorue Login page instance you make or did make before.
You can hold references to pages youreself i you want to and reuse them as response pages in onClicks or onSubmits

johan


On 12/21/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
ahh, you didnt say you click the link before (or at least i didnt catch it - its bed time very soon )

this is indeed the proper behaviour. the link is used to go to a "fresh" login page - the way that is attained is that wicket will use a default IPageFactory implementation to instantiate a page by its class - because that is the only way to get a page with a clean state. so when it does that, the constructor is called and you see the message.

-Igor


On 12/20/05, karthik Guru < [EMAIL PROTECTED]> wrote:
:( 
- wicket 1.1 that i downloaded from the link on the home page. Moment i click the link (Login.html) on Welcome.html, i see the Login.java constructor getting called.
 
 
On 12/21/05, Igor Vaynberg <[EMAIL PROTECTED] > wrote:
what version of wicket are you using?

when i run your example i get:

Login Constructor called!
User id was asdadasda and the password was asdasdasd
Welcome Constructor!

which is the output i would expect.

-Igor






Reply via email to