Hi,
They are used quite differently.
You use an external link to render a link that the user has to click on,
and - when it is clicked on, will direct your browser to that destination.
The RedirectPage is used to direct the browser to an external location
directly from the server side. You can call it from anywhere, e.g. when
you're in a Form, or any other IRequestListener handler.
So, external links are rather static, while the use of the RedirectPage
can be as dynamic as you want it to be.
Eelco
Les Pruszynski wrote:
Hello guys,
Going through Wicket class hierarchy I realised that we have two
classes that serve similar purposes (see below). Shouldn't they be
merged into one? What do you think?
public class *ExternalLink*
extends WebMarkupContainer
<http://wicket.sourceforge.net/apidocs/wicket/markup/html/WebMarkupContainer.html>
A simple anchor link (<a href="http://url";>) pointing to any URL.
Usually this is used for links to destinations outside of Wicket.
public final class *RedirectPage*
extends WebPage
<http://wicket.sourceforge.net/apidocs/wicket/markup/html/WebPage.html>
Page that let the browser redirect. Use this if you want to direct the
browser to some external URL, like Google etc. or if you want to
redirect to a Wicket page, but with a delay.
Les
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
