I have a main class that configures and fires up Jetty. (That\'s standard practice from Wicket for testing a webapp, but it\'s really not wicket-specific.)
final
Add a WebAppContext
for each virtual directory:
final Server server = new Server();
//skipped socketconnector initialization
final WebAppContext js = new WebAppContext();
js.setServer(server);
js.setContextPath("/js");
js.setWar("target/classes/js"); // or whatever the correct path is in your case
server.addHandler(js);
// css the same way
final WebAppContext bb = new WebAppContext();
bb.setServer(server);
bb.setContextPath("/");
bb.setWar("src/main/webapp");
server.addHandler(bb);
server.start();
For completeness, here's the workaround I have been using:
final Server server = new Server();
//skipped socketconnector initialization
final WebAppContext bb = new WebAppContext();
bb.setServer(server);
bb.setContextPath("/");
bb.setWar("src/main/webapp");
final URL url = new File("target/classes").getAbsoluteFile().toURI().toURL();
final Resource resource = new FileResource(url);
final ResourceHandler handler = new ResourceHandler();
handler.setBaseResource(resource);
server.addHandler(handler);
server.addHandler(bb);
server.start();
But it's not very elegant, it mounts everything in target/classes and uses the webapp only as fallback.