i dont think its a bug. autolinking is based on page's class, so if you have multiple links to the same page class with different parameters they will all be disabled. one more disadvantage of using wicket:link to do it automatically. if you used a link component you created you could override the linksTo() method.

-Igor


On 4/14/06, Michael Day <[EMAIL PROTECTED]> wrote:
Yep, I know I can add Link components, but it gets very tedious when
you have, say, 100 links on a page.  Auto-linking is such a useful
feature, so I personally think that the link disabling feature should
be a) configurable (via MarkupSettings), and b) disabled by default
since it's not what users would normally expect.

When I add a new BookmarkablePageLink manually, it doesn't seem to
auto-disable.  Why should this behavior differ from an auto-link?

By the way, I think there may be a bug with mounted pages and
disabled links.  I have a page with parameters and all links to that
page (even those with different parameters) get disabled.

Michael Day

On Apr 14, 2006, at 4:00 AM, Juergen Donnerstag wrote:

> 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
>> [email protected]
>> 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
> [email protected]
> 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?cmdlnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to