Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

It's when you see crazy long command lines like that, you start to appreaciate Maven (or Gradle). The same command in Maven is "mvn gwt:codeserver -pl *-client" (yes, I know you see still need to setup the launcherDir, warDir, etc in the pom.xml files, but that seems much easier than one huge

Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

> If using maven... [I'm not]... If not, please give us more detail about what you are using (or intend to use). After further investigation, much of my issues around this seem to be that the. appropriate java command to run the web app (or Jetty itself) is not being assembled correctly by eit

Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

@Colin, thanks for getting back to me on this. I couldn't reply right away because my wife was getting cataract surgery; it's not that this wasn't important. > If you mean a particular plugin that you use with GWT... I'm using the Eclipse GWT 4.0.0 plugin you guys recently completed (using the

Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

> Clearly the GWT plugin/installed Jetty are not Jakarta-ready. I could try to update and rebuild the plugin to make it so (maybe), but I'm so overwhelmed with other chores that I can't afford having that turn into another rabbit hole. It's easier/safer/wiser to go back to javax. If you mean t

Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

Thanks for all the replies. None of them directly addressed my needs, but in combination they all provided enough understanding to help me make some decisions: Clearly the GWT plugin/installed Jetty are not Jakarta-ready. I could try to update and rebuild the plugin to make it so (maybe), but

Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

On Wednesday, June 12, 2024 at 11:27:27 AM UTC+2 Jens wrote: Needless to say that I have split client, shared and server code into their own projects. This is the recommeneded project layout these days * checks notes * I've been advocating for it for more than 12 years now

Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

1. You do not have to use Jakarta if you want to migrate to Java 17. You can very well stay on javax and first make the JDK transition work 2. GWT's embedded Jetty is always javax because it is version 9.4.xx. The use of GWT's embedded Jetty is officially deprecated and you should use your own J

Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

This might help: its a different solution to the issue Craig dealt with. Its an extension of the gwt multi-module sample with an embedded Jetty, for Java 11 without Spring. https://github.com/timmacp/AppEngineGwt/tree/main On Wednesday, June 12, 2024 at 9:03:01 AM UTC+1 Wejden Mrabti wrote: > hel

Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

hello! @Craig it looks great what you have done! @bob I am working on same migration acutally, It looks that the embedded Jetty in GWT DevMode has been deprecated in GWT 2.11 due to classloader issues and other complexities. To avoid these problems, you can try transition to a dedicated servlet

Re: GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

I would recommend creating a new project with everything that you want to use, get it working how you like, then use that as a template on how you will upgrade your existing project. For my project that I needed to upgrade from Java 8 to Java 17 (because Google App Engine dropped support for Ja

GWT, Java 17, jakarta.servlet, Eclipse, GWT plugin

I am wrestling with a massive effort that has been one stumbling block after another. The core task is to convert a sadly monolithic and archaic app from Java 8 to Java 17. My current subtask (maybe necessary, maybe not) is to convert everything to use jakarta.servlet rather than javax.servlet,