could be. The links are resolved relative to the parents container. Similar to your Panel you could create your own container which adds all the links you need. And you add only this component to the page/panel where you want it to be. Than most of the code is out of sight but refactoring etc. still works.
Juergen On 2/21/06, Frank Silbermann <[EMAIL PROTECTED]> wrote: > Suppose my page that displays the links is at a deeply nested level, and > I want to use <wicket:link> to go to a page closer to the root. Would > it work if I defined a Panel at the top level and put my <wicket:link> > in there (to be included by pages that were deeply nested)? > > If not, what is the easiest way to hardcode a static list of many Wicket > links, some of which go up the hierarchy? If the list is static and no > parameters are being passed, it seems like overkill to have to write > code for each link. > > /Frank > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Juergen > Donnerstag > Sent: Thursday, February 16, 2006 4:17 PM > To: wicket-user@lists.sourceforge.net > Subject: Re: [Wicket-user] <Wicket:link> question > > wicket:link is realy for convinience only and doesn#t have the full > flexibility of Links etc. But they support subpackages like > sub/myPage.html. You can not do ../xxx and absolute paths are excluded > as well. > > Juergen > > On 2/16/06, Frank Silbermann <[EMAIL PROTECTED]> wrote: > > > > > > I've seen that within a <wicket:link> tag we can write ordinary HTML > links > > and have Wicket lings automatically generated. The Component > Reference > > examples use it as follows: > > > > > > > > <wicket:link> > > > > <ul> > > > > <li><a > > href="PanelPage.html">wicket.markup.html.panel.Panel</a></li> > > > > <li><a > > href="BorderPage.html">wicket.markup.html.border.Border</a></li> > > > > </ul> > > > > </wicket:link> > > > > > > > > But in all the examples, the linked pages were in the same package as > the > > page doing the linking. Can we use <wicket:link> to link to pages in > other > > packages of our application? If so, then how do we indicate the path > (so as > > to distinguish between page classes with the same name in different > > packages)? > > > > > > > > Would I use something like Unix relative path notation? > > > > > > > > Or is <wicket:link> only useful for linking within a package? > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642 > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
