> There was also someone that suggested another approach. Bundle jetty together
> with jettylauncher which would cut back on configuration and compatibility
> issues. I was going to try that approach but, as always, wasn't able to get
> around to it.
Yeah, that would be the nicest thing to do imho. I don't even think it
is much work tbh.
This:
Server server = new Server();
SelectChannelConnector connector = new SelectChannelConnector();
connector.setPort(8080);
server.addConnector(connector);
WebAppContext web = new WebAppContext();
web.setContextPath("/wia");
web.setWar("src/webapp");
server.addHandler(web);
try {
server.start();
server.join();
} catch (Exception e) {
e.printStackTrace();
System.exit(100);
}
is basically the kind of code you need to start Jetty up. The only
thing needed to build around it are the typical Eclipse thingies and
the ability to set the webapp dir and context path and port. I think
that would be pretty much it.
Unfortunately, with Wicket taking off, my daily project taking a lot
of time, writing a book in the back ground and a wedding in the
planning I just can't get around to work on JettyLauncher. It would be
great if someone else would take that up.
Regards,
Eelco
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jettylauncher-plugin mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jettylauncher-plugin
