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.
It actually maps Wicket servlet to /wicket-bench/*. This is the Jetty
code from the plugin:
server.addListener(":" + port);
HttpContext context = server.getContext("/");
ProjectMetadata metadata = new ProjectMetadata().load();
WicketBench.setProjectMetadata(metadata);
context.setResourceBase(metadata.getContextRoot());
ServletHandler servletHandler = new ServletHandler();
ServletHolder holder =
servletHandler.addServlet("WicketBenchApplication", "/wicket-bench/*",
WicketServlet.class.getName());
holder.setInitParameter("applicationFactoryClassName",
WicketBenchApplicationFactory.class.getName());
context.addHandler(new ResourceHandler());
context.addHandler(servletHandler);
Do you see any problems with above code?
PS. I'll set up wicket-bench related mailing list.
Joni
