Maybe related; but my real issue was different. So I was mounting pages on a different path. It seems <wicket:link> uses that AutoLinkResolver stuff and does not keep up with mount changes. So it was not able to resolve the links on my Markup due to the changed mount points & resource locator changes (in WebAppplication)
Am not sure if this is a bug, but if I make changes in my mount's in WebApplication, I'd expect <wicket:link> to keep up. On the positive side I don't need<wicket:link> so my markups are now cleaner as my Application understands the URL's directly; which also gets rid of the warnings. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/AutoLinkResolver-WARNINGS-tp2332181p2334613.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
