On Wed, 2006-10-18 at 21:13 -0500, Ryan Sonnek wrote: > if there's a seperate wicket-bench list I can take this issue there... > > I've had issues with wicket-bench-0.4.0 where my javascript (in > <wicket:head>) was not being loaded on the first page load. It happened > pretty regularly with firefox, and both firebug and the web-developer plugin > were reporting issues. I was getting very concerned that this was a core > wicket issue, until I started launching my application outside of > wicket-bench using the jetty launcher. i haven't hit a single javascript > load issue since. > > what's the issue? i think it's related to wicket-bench being loaded on the > "/*" servlet mapping instead of "/app/*". if anyone can confirm or deny > this, i'm open to suggestions. I'm also willing to help out the > wicket-bench devs if they need any help with this.
I think I know the reason for this now. The first page served by wicket bench is a bookmarked page having url http://localhost:8090/wicket-bench/home That's why relative urls for images or javascript do not work on the first page load. However, wicket generated links contain only the contextPath, e.g. http://localhost:8090/wicket-bench?wicket:interface=:0 for these pages relative urls work. So, this may be core wicket issue too. I found following bug entry: http://www.mail-archive.com/wicket-develop% 40lists.sourceforge.net/msg07813.html Sourceforge tracker is closed and I couldn't find this issue from apache jira. Does anyone know the status of above issue? Joni
