Hey Tim, In order to make this work, you can either implement a ServletContainerLauncher of your own, and use the -server option with the HostedMode entry point, as Salvador suggest. More info on ServletContainerLaunchers can be found here:
http://code.google.com/p/google-web-toolkit/source/browse/releases/1.6/dev/core/src/com/google/gwt/core/ext/ServletContainerLauncher.java http://code.google.com/p/google-web-toolkit/source/browse/releases/1.6/dev/core/src/com/google/gwt/core/ext/ServletContainer.java However, the easiest thing to do is probably to start with GWT's existing launcher for Jetty and modify it to suit your needs. This is the launcher that GWT is using to start up Jetty: http://code.google.com/p/google-web-toolkit/source/browse/releases/1.6/dev/core/src/com/google/gwt/dev/shell/jetty/JettyLauncher.java You'll have to modify your launch classpath to put your version of Jetty higher up on the classpath than the GWT SDK. You'll also have to put your version of JettyLauncher higher on the classpath as well. Rajeev 2009/4/21 Salvador Diaz <[email protected]> > > use -noserver or -server ? > > Google Web Toolkit 1.6.4 > HostedMode [-noserver] [-port port-number | "auto"] [-whitelist > whitelist-string] [-blacklist blacklist-string] [-logLevel level] [- > gen dir] [-style style] [-ea] [-server servletContainerLauncher] [- > startupUrl url] [-war dir] [-extra dir] [-workDir dir] [-localWorkers > count] module[s] > > where > -noserver Prevents the embedded web server from running > -port Specifies the TCP port for the embedded web server > (defaults to 8888) > -whitelist Allows the user to browse URLs that match the > specified regexes (comma or space separated) > -blacklist Prevents the user browsing URLs that match the > specified regexes (comma or space separated) > -logLevel The level of logging detail: ERROR, WARN, INFO, > TRACE, DEBUG, SPAM, or ALL > -gen The directory into which generated files will be > written for review > -style Script output style: OBF[USCATED], PRETTY, or > DETAILED (defaults to OBF) > -ea Debugging: causes the compiled output to check assert > statements. > -server Specifies a different embedded web server to run > (must implement ServletContainerLauncher) > -startupUrl Automatically launches the specified URL > -war The war directory to write output files into > (defaults to war) > -extra The directory into which extra, non-deployed files > will be written > -workDir The compiler work directory (must be writeable; > defaults to a system temp dir) > -localWorkers Specifies the number of local workers to use when > compiling permutations > and > module[s] Specifies the name(s) of the module(s) to host > > Cheers, > > Salvador > > On Apr 21, 3:37 am, TimOnGmail <[email protected]> wrote: > > Hi Leon... > > > > Are you saying there *is* an option somewhere (in which case, where?), > > or it would be a good idea if there were one? > > > > - Tim > > > > On Apr 20, 6:01 pm, Leon Li <[email protected]> wrote: > > > > > There should be an option there .... > > > > > On 4月21日, 上午6时29分, TimOnGmail <[email protected]> wrote: > > > > > > I want to add, I'm doing all of this in the Eclipse GWT plugin. > > > > > > - Tim > > > > > > On Apr 20, 3:28 pm, TimOnGmail <[email protected]> wrote: > > > > > > > Hi there... > > > > > > > I suspect I'm hitting some errors using the embedded Jetty 5 server > in > > > > > Hosted Mode. > > > > > > > Does anyone know of an easy way to tell GWT 1.6 "Use THIS Jetty jar > as > > > > > your server, and not the default one"? > > > > > > > - Tim- Hide quoted text - > > > > > - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
