During development, with "SuperDevMode"+"Jetty" and "Google Plugin for Eclipse", GWT client-side code compilation (including the nocache.js files) is done at runtime by DevMode.
Any other scenario demands that we, separately compile the GWT client-side code, separately run a servlet, separately deploy the GWT code to the server (both client-side and server-side), separately run GWT CodeServer, then run a browser, then genearate the CodeServer link etc. The complexity difference is obvious. I hope this explains my case. On Saturday, 17 April 2021 at 19:36:18 UTC+1 [email protected] wrote: > If it's not a problem for you to serve servlets separately, could you > explain why you couldn't have this other server also serve the host page > and nocache.js file? Is that due to, maybe, how your projects are > structured? (Could you give more details then?) > Trying to understand what's blocking people here. > > Le sam. 17 avr. 2021 à 20:06, [email protected] <[email protected]> a > écrit : > >> This feels much better now. >> >> Serving only static GWT client-side via DevMode+Jetty sounds good. >> >> We could run the GWT server-side only code separately, not a problem at >> all. >> >> But, how would the GWT client-side know how to access GWT server-side? >> >> On Saturday, 17 April 2021 at 18:45:39 UTC+1 [email protected] wrote: >> >>> Moreover, we have to be careful when we say "remove Jetty", because >>> Jetty is used in CodeServer and JUnitShell. >>> Really the question here is about removing the ability to serve webapps, >>> with servlets, from DevMode. >>> >>> Le sam. 17 avr. 2021 à 19:34, [email protected] <[email protected]> >>> a écrit : >>> >>>> This is a very good idea. >>>> >>>> I am afraid though that it wouldn't change the situation much because >>>> the classpaths of GWT and Jetty co-exist and must be aligned regardless. >>>> >>>> But, I would stand corrected. >>>> >>>> On Saturday, 17 April 2021 at 17:25:19 UTC+1 Paul Robinson wrote: >>>> >>>>> Would it be plausible to split GWT into two projects - one as it is >>>>> now but without Jetty built in, and another that adds the bits relating >>>>> to >>>>> Jetty? >>>>> >>>>> Then the GWT Jetty project could be maintained by those that require >>>>> it. >>>>> >>>>> Paul >>>>> >>>> -- >>>> >>> You received this message because you are subscribed to the Google >>>> Groups "GWT Contributors" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/9cce0909-56fc-4804-a032-103184c05af1n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/9cce0909-56fc-4804-a032-103184c05af1n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "GWT Contributors" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-web-toolkit-contributors/94c5c53d-b72a-4887-a617-4d1064c7c8fan%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/94c5c53d-b72a-4887-a617-4d1064c7c8fan%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/4486df4d-553d-409f-b3a8-4b4887ff0b9fn%40googlegroups.com.
