On 6/29/07, Vadim Tesis <[EMAIL PROTECTED]> wrote: > i see. i guess i assumed that the Link knows about the page it's linking > from setResponsePage() in onClick().
Heh, you have too much awe for Wicket: that would require either running the onClick upfront (the isenabled check also determines how the link is rendered!), which can have a lot of consequences, or analyzing the bytecode (which may have some security issues), and try to come up with something magical. > so, in this use case is there any difference whether to override linksTo() > or isEnabled()? i think overriding isEnabled() is more generic, if latter > i'll need to add more logic to disable the link this will be the place to do > it. anything else? This is a correct analysis of the situation. Martijn -- Wicket joins the Apache Software Foundation as Apache Wicket Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
