Hi all,
I've been trying to create a custom JettyLauncher to enable launching
Jetty 7 in GWT's dev mode instead of the default Jetty 6.
I've based my work on http://code.google.com/p/gwt-jetty/ and, if used
with my guice for servlet injection patch
(http://codereview.waveprotocol.org/563001) it would enable using:
<target name="hosted-gwt" depends="compile"
description="Runs the hosted mode server, for debugging the GWT
client in a JVM.">
<java failonerror="true" fork="true" classname="com.google.gwt.dev.DevMode">
<classpath>
<pathelement location="${src.dir}"/>
<pathelement location="${gen.dir}/messages"/>
<pathelement location="${build.src.dir}"/>
<pathelement location="${build.proto.dir}"/>
<pathelement location="${build.messages.dir}"/>
<path refid="libpath"/>
</classpath>
<jvmarg value="-Xmx512M"/>
<jvmarg value="-ea"/>
<jvmarg
value="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8001"/>
<jvmarg value="-Dorg.eclipse.jetty.util.log.DEBUG=true"/>
<jvmarg value="-Djava.security.auth.login.config=jaas.config" />
<jvmarg value="-Dwave.server.config=server.config"/>
<arg line="-server org.waveprotocol.box.server.gwt.jetty.JettyLauncher" />
<arg line="-bindAddress 0.0.0.0" />
<arg line="${gwt.args}"/>
<arg line="-startupUrl /" />
<arg value="org.waveprotocol.box.webclient.WebClientProd"/>
</java>
</target>
to launch GWT in dev mode with jetty 7.
By setting up a GuiceServletContextListener very similar to our
ServerMain and registering it as a listener in the web.xml file we would
be able to start all the servlets in the embedded app server.
I'd just like to know if this is something you'd be interested to have
submited as patch.
Regards,
Nelson
