Switching from internal Jetty to External tomcat/jetty

59 views
Skip to first unread message

blackh...@gmail.com

unread,
Jul 5, 2022, 6:05:26 AM7/5/22
to GWT Users
We have a big project, where the client and server code is not seperated in seperate projects.
We use ant, to build our project.
We are able to start devmode with the internal Jetty server, but...
I have seen a lot of comments, to step away from the internal jetty and use and external server.

<target name="debug-web" description="Run development mode">
    <property name="webclient" value="XXXWeb" />
    <property name="package" value="xxx" />
    <property name="gwtxmllocation" value="${package}" />
    <property name="weburl" value="XXXweb" />
    <property environment="env" />
    <property name="webtempfolder" value="${env.TEMP}\demo" />

    <java classname="com.google.gwt.dev.DevMode" fork="true" failonerror="false" resultproperty="return.code">
        <classpath>
            <pathelement location="src"/>                
            <path refid="gwt.classpath" />
        </classpath>
        <arg line="-noserver" />
        <arg line="-war" />
        <arg value="${tomcatwebappdir}" />
        <arg line="-style" />
        <arg value="DETAILED" />
        <arg line="-logLevel" />
        <arg value="DEBUG"  />
        <arg line="-startupUrl" />
        <arg value="${weburl}" />
        <arg line="com.sweet.${gwtxmllocation}.${webclient}" />
    </java>
</target>

With the above ant script, i am able to generate the web files for tomcat and let it start with it.
But after compiling tomcat is not able to find the server components...
How to make tomcat be aware of the server components, which are the class files in the project?
Do we need to switch to maven or can we still use ant?
Reply all
Reply to author
Forward
0 new messages