Only very little performance impact. Wicket automatically creates a Link component for you and the "disable" behavior is exactly the same as for for Links. And Links get disabled if they point to the same page. If you don't want that behavior, than you can not use autolinks. Just add standard normal Links yourself and you have all the control over that link you want - except it is not generated automatically.
Juergen On 4/14/06, Michael Day <[EMAIL PROTECTED]> wrote: > I've tried two different methods of auto-linking. One is > getMarkupSettings().setAutoLinking(true); The other is by wrapping > my anchors in <wicket:link>. Both methods work fine for linking, but > when you go to the linked page, the links become disabled (anchors > are replaced with <span>). How can I prevent this behavior? I don't > think there are any configuration options for it. > > By the way, does setAutoLinking(true) have any serious performance > implications? > > Thanks, > Michael Day > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
