You could just use bookmarkable HTML links without Wicket components beneath them. With a custom AbstractMarkupFilter you can adjust the href attribute to fit with your deployment.
HTH Sven >Sure, that's not a problem. Just thinking out loud, though... > >Generally, I understand that it is important to define each component >distinctly. However, don't you think that the case for links is a bit >different? > >It seems to me that in a typical web page, there is a good change of >having more than one instance of a link. > >What do you think about making an exception to the 1:1 relationship for >the case of links? > > >Just wondering... > > > >On Tue, 2006-02-07 at 09:25 +0100, Juergen Donnerstag wrote: >> This is true. There must be a 1:1 relationsship between markup and >> component. Simply define multiple ids like topPageLink1, topPageLink2 >> etc and corresponding components. > > > > >------------------------------------------------------- >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&kid=103432&bid=230486&dat=121642 >_______________________________________________ >Wicket-user mailing list >[email protected] >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&kid=103432&bid=230486&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
