Re: GWT RPC and CSP with unsafe-eval
I have to correct myself: every RPC call fails, not just one in particular. On Friday, May 31, 2024 at 2:48:48 PM UTC+2 Giacomo Petronio wrote: > I upgraded to GWT 2.11.0 and introduced the CSP header disallowing > unsafe-eval, but now one (not all) RPC call fails since it hits an eval() > function that is blocked by the browser. > > I saw that there is an issue with RPC with large payloads (> 64kb > https://github.com/gwtproject/gwt/issues/9578) but my RPC > request/responses are never so big (1kb at most). > > What else could it be? > > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/bdaafa60-65c7-482b-92fc-ab0b85f58fd7n%40googlegroups.com.
GWT RPC and CSP with unsafe-eval
I upgraded to GWT 2.11.0 and introduced the CSP header disallowing unsafe-eval, but now one (not all) RPC call fails since it hits an eval() function that is blocked by the browser. I saw that there is an issue with RPC with large payloads (> 64kb https://github.com/gwtproject/gwt/issues/9578) but my RPC request/responses are never so big (1kb at most). What else could it be? -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/22a494ad-8d0e-467d-983f-9961942a540cn%40googlegroups.com.
Re: GWT Java Interview at JCON 2024 Cologne
Nice one. I can't believe you agreed with the presentor that you missed writing Swing apps. Nobody misses Swing. On Saturday 25 May 2024 at 8:23:14 pm UTC+10 lofid...@gmail.com wrote: > At JCON 2024 in Cologne, I had the opportunity to talk about GWT and Java. > > I was interviewed by Brian Demers, a Java Champion. Pardon me as we forgot > to unmute the first minute - Enjoy > > https://bit.ly/jcongwt > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a7820fa7-460d-4990-b5f3-917503b70bf8n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
> (fwiw, your GitHub Actions workflow no longer runs as it targets the master branch and you renamed it to main) good point! Thanks. Thomas Broyer schrieb am Freitag, 24. Mai 2024 um 11:22:43 UTC+2: > On Thursday, May 23, 2024 at 6:31:18 PM UTC+2 frank.h...@googlemail.com > wrote: > > Running a `mvn clean verify` generate the project and compares it with > predefined sources. Similar to your gwt-maven-archetype. > What not gets tested, is building a war and run it. > > > Ah, apparently it also gets built ( > https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/goal.txt), > > but indeed the generated WAR is not run. > > > (fwiw, your GitHub Actions workflow no longer runs as it targets the > master branch and you renamed it to main) > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a11270ac-2b63-42aa-9280-ba6d9e5c7acen%40googlegroups.com.
GWT Java Interview at JCON 2024 Cologne
At JCON 2024 in Cologne, I had the opportunity to talk about GWT and Java. I was interviewed by Brian Demers, a Java Champion. Pardon me as we forgot to unmute the first minute - Enjoy https://bit.ly/jcongwt -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a660a827-42d8-4303-bcb2-a6427f40f546n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
On Thursday, May 23, 2024 at 6:31:18 PM UTC+2 frank.h...@googlemail.com wrote: Running a `mvn clean verify` generate the project and compares it with predefined sources. Similar to your gwt-maven-archetype. What not gets tested, is building a war and run it. Ah, apparently it also gets built (https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/goal.txt), but indeed the generated WAR is not run. (fwiw, your GitHub Actions workflow no longer runs as it targets the master branch and you renamed it to main) -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/b913dab3-6a70-4b84-850f-722523c75acdn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
When Thomas said: > *Out of curiosity, any specific reason you don't automate a "mvn clean verify" to validate the generated project?* I suspect he was talking about a Git pre-push hook that automatically did a mvn verify: https://git-scm.com/docs/githooks#_pre_push Unless I misunderstood. On Friday 24 May 2024 at 2:32:12 am UTC+10 Frank Hossfeld wrote: > Thanks for contributing, Craig, LGTM, so already merged. :-) > > Craig Mitchell schrieb am Mittwoch, 22. Mai 2024 um 03:48:18 UTC+2: > >> Thanks Frank. I was misunderstanding and didn't know about >> the basic-webapp in the target. >> >> I revamped the readme.md: >> https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/17 >> >> Hopefully made it better not worse. >> >> On Wednesday 22 May 2024 at 2:07:30 am UTC+10 Thomas Broyer wrote: >> >>> On Tuesday, May 21, 2024 at 6:02:31 PM UTC+2 frank.h...@googlemail.com >>> wrote: >>> >>> Ok, got it, was thinking, we were talking about the generated project >>> ... Yep correct, usually, running the verify goal, will compare the >>> generated sources with the ones stored under test resources. There is no >>> test were the generated project gets started/tested, if it works. >>> >>> >>> Out of curiosity, any specific reason you don't automate a "mvn clean >>> verify" to validate the generated project? >>> (of course testing that devmode works, or that the built artifact >>> actually works is trickier and probably not worth it, but a simple build >>> would still be better than nothing IMO) >>> >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/88c30284-56b4-4885-b4cf-ff796e1348e7n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Thanks for contributing, Craig, LGTM, so already merged. :-) Craig Mitchell schrieb am Mittwoch, 22. Mai 2024 um 03:48:18 UTC+2: > Thanks Frank. I was misunderstanding and didn't know about > the basic-webapp in the target. > > I revamped the readme.md: > https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/17 > > Hopefully made it better not worse. > > On Wednesday 22 May 2024 at 2:07:30 am UTC+10 Thomas Broyer wrote: > >> On Tuesday, May 21, 2024 at 6:02:31 PM UTC+2 frank.h...@googlemail.com >> wrote: >> >> Ok, got it, was thinking, we were talking about the generated project ... >> Yep correct, usually, running the verify goal, will compare the generated >> sources with the ones stored under test resources. There is no test were >> the generated project gets started/tested, if it works. >> >> >> Out of curiosity, any specific reason you don't automate a "mvn clean >> verify" to validate the generated project? >> (of course testing that devmode works, or that the built artifact >> actually works is trickier and probably not worth it, but a simple build >> would still be better than nothing IMO) >> > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/708326cd-d39b-4d0b-874c-42e90bcb8fe4n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Running a `mvn clean verify` generate the project and compares it with predefined sources. Similar to your gwt-maven-archetype. What not gets tested, is building a war and run it. Thomas Broyer schrieb am Dienstag, 21. Mai 2024 um 18:07:30 UTC+2: > On Tuesday, May 21, 2024 at 6:02:31 PM UTC+2 frank.h...@googlemail.com > wrote: > > Ok, got it, was thinking, we were talking about the generated project ... > Yep correct, usually, running the verify goal, will compare the generated > sources with the ones stored under test resources. There is no test were > the generated project gets started/tested, if it works. > > > Out of curiosity, any specific reason you don't automate a "mvn clean > verify" to validate the generated project? > (of course testing that devmode works, or that the built artifact actually > works is trickier and probably not worth it, but a simple build would still > be better than nothing IMO) > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/e5e38708-02ac-4953-97af-0bdc00c0980cn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Thanks Frank. I was misunderstanding and didn't know about the basic-webapp in the target. I revamped the readme.md: https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/17 Hopefully made it better not worse. On Wednesday 22 May 2024 at 2:07:30 am UTC+10 Thomas Broyer wrote: > On Tuesday, May 21, 2024 at 6:02:31 PM UTC+2 frank.h...@googlemail.com > wrote: > > Ok, got it, was thinking, we were talking about the generated project ... > Yep correct, usually, running the verify goal, will compare the generated > sources with the ones stored under test resources. There is no test were > the generated project gets started/tested, if it works. > > > Out of curiosity, any specific reason you don't automate a "mvn clean > verify" to validate the generated project? > (of course testing that devmode works, or that the built artifact actually > works is trickier and probably not worth it, but a simple build would still > be better than nothing IMO) > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/42002fd9-40db-4c1d-ac76-81531e1f0bffn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
On Tuesday, May 21, 2024 at 6:02:31 PM UTC+2 frank.h...@googlemail.com wrote: Ok, got it, was thinking, we were talking about the generated project ... Yep correct, usually, running the verify goal, will compare the generated sources with the ones stored under test resources. There is no test were the generated project gets started/tested, if it works. Out of curiosity, any specific reason you don't automate a "mvn clean verify" to validate the generated project? (of course testing that devmode works, or that the built artifact actually works is trickier and probably not worth it, but a simple build would still be better than nothing IMO) -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/05b26042-335b-4443-b036-70eecf9a0ef0n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Ok, got it, was thinking, we were talking about the generated project ... Yep correct, usually, running the verify goal, will compare the generated sources with the ones stored under test resources. There is no test were the generated project gets started/tested, if it works. The generated project from the verify goal can be found here: 'modular-springboot-webapp/target/test-classes/projects/basic-webapp/project/basic-webapp' inside the web-app directory you can do a `mvn clean install` and test the project. Craig Mitchell schrieb am Dienstag, 21. Mai 2024 um 08:13:47 UTC+2: > Sorry, I think I wasn't clear. Yes, I can make changes to the > gwt-maven-springboot-archetype project, and do a mvn compile on it to make > sure there are no syntax errors with my changes. > > The problem is, if I want to test to make sure my modified version of > gwt-maven-springboot-archetype actually generates a new project correctly > (Ie: Run mvn archetype:generate ...), this doesn't work unless I do a mvn > install. as maven doesn't see the HEAD-SNAPSHOT version, as (I'm guessing a > bit here, I'm not a maven expert), I think maven only looks in its > repositories (local and remote), and there isn't any HEAD-SNAPSHOT version, > as it's not installed. Thus, I get the "The desired archetype does not > exist (com:modular-springboot-webapp:HEAD-SNAPSHOT)" error. > > fyi: At no point are there any GWT compilations. That comes later when I > compile the project that was generated. > > On Monday 20 May 2024 at 11:07:45 pm UTC+10 Frank Hossfeld wrote: > >> Thanks for you PR. Your PR is merged and a new release is done. New >> version should be available soon. >> >> doing a `mvn clean compile` is usually enough to generate all necessary >> sources and run the project. It's much faster cause it avoids a GWT compile >> during build. In case you need a war, run `mvn clean verify`- not sure, if >> install is really needed. So, for develpment, `mvn clean compile` Is all >> you need to do. And it save a lot of time especially when the project gets >> more classes. >> >> >> Craig Mitchell schrieb am Montag, 20. Mai 2024 um 05:00:07 UTC+2: >> >>> Just tried a mvn install, and it seems to have worked. >>> >>> So I think the instructions >>> https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation >>> >>> : >>> cd gwt-maven-springboot-archetype && mvn clean compile >>> >>> should be: >>> cd gwt-maven-springboot-archetype && mvn clean install >>> >>> And my PR looks good. >>> >>> On Monday 20 May 2024 at 12:40:45 pm UTC+10 Craig Mitchell wrote: >>> >>>> Hi Frank. Unfortunately, that didn't work. I raised an issue: >>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15 >>>> >>>> I've also submitted a fix: >>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16 >>>> >>>> However, I couldn't test my fix with the generation. The instructions >>>> here: >>>> https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation >>>> >>>> say to test, you do: >>>> >>>> cd gwt-maven-springboot-archetype && mvn clean compile >>>> >>>> And then I should be able to do: >>>> >>>> mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype >>>> -DarchetypeVersion=HEAD-SNAPSHOT >>>> -DarchetypeArtifactId=modular-springboot-webapp >>>> >>>> But that fails with: >>>> >>>> *The desired archetype does not exist >>>> (com:modular-springboot-webapp:HEAD-SNAPSHOT)* >>>> >>>> I suspect I'm supposed to do a mvn install? Or mvn deploy? Something >>>> that makes HEAD-SNAPSHOT available? >>>> >>>> On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote: >>>> >>>>> I'll added some additional code to avoid adding the launcherDir as >>>>> document root in production mode. >>>>> New version should be soon available. >>>>> >>>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2: >>>>> >>>>>> The issue seems to be the launcherDir directory doesn't exist. I've >>>>>> raised a an issue with the full stack trace: >>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13 >>&g
Re: gwt-maven-springboot-archetype updated ...
Sorry, I think I wasn't clear. Yes, I can make changes to the gwt-maven-springboot-archetype project, and do a mvn compile on it to make sure there are no syntax errors with my changes. The problem is, if I want to test to make sure my modified version of gwt-maven-springboot-archetype actually generates a new project correctly (Ie: Run mvn archetype:generate ...), this doesn't work unless I do a mvn install. as maven doesn't see the HEAD-SNAPSHOT version, as (I'm guessing a bit here, I'm not a maven expert), I think maven only looks in its repositories (local and remote), and there isn't any HEAD-SNAPSHOT version, as it's not installed. Thus, I get the "The desired archetype does not exist (com:modular-springboot-webapp:HEAD-SNAPSHOT)" error. fyi: At no point are there any GWT compilations. That comes later when I compile the project that was generated. On Monday 20 May 2024 at 11:07:45 pm UTC+10 Frank Hossfeld wrote: > Thanks for you PR. Your PR is merged and a new release is done. New > version should be available soon. > > doing a `mvn clean compile` is usually enough to generate all necessary > sources and run the project. It's much faster cause it avoids a GWT compile > during build. In case you need a war, run `mvn clean verify`- not sure, if > install is really needed. So, for develpment, `mvn clean compile` Is all > you need to do. And it save a lot of time especially when the project gets > more classes. > > > Craig Mitchell schrieb am Montag, 20. Mai 2024 um 05:00:07 UTC+2: > >> Just tried a mvn install, and it seems to have worked. >> >> So I think the instructions >> https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation >> >> : >> cd gwt-maven-springboot-archetype && mvn clean compile >> >> should be: >> cd gwt-maven-springboot-archetype && mvn clean install >> >> And my PR looks good. >> >> On Monday 20 May 2024 at 12:40:45 pm UTC+10 Craig Mitchell wrote: >> >>> Hi Frank. Unfortunately, that didn't work. I raised an issue: >>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15 >>> >>> I've also submitted a fix: >>> https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16 >>> >>> However, I couldn't test my fix with the generation. The instructions >>> here: >>> https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation >>> >>> say to test, you do: >>> >>> cd gwt-maven-springboot-archetype && mvn clean compile >>> >>> And then I should be able to do: >>> >>> mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype >>> -DarchetypeVersion=HEAD-SNAPSHOT >>> -DarchetypeArtifactId=modular-springboot-webapp >>> >>> But that fails with: >>> >>> *The desired archetype does not exist >>> (com:modular-springboot-webapp:HEAD-SNAPSHOT)* >>> >>> I suspect I'm supposed to do a mvn install? Or mvn deploy? Something >>> that makes HEAD-SNAPSHOT available? >>> >>> On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote: >>> >>>> I'll added some additional code to avoid adding the launcherDir as >>>> document root in production mode. >>>> New version should be soon available. >>>> >>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2: >>>> >>>>> The issue seems to be the launcherDir directory doesn't exist. I've >>>>> raised a an issue with the full stack trace: >>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13 >>>>> >>>>> On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote: >>>>> >>>>>> please can you post the error message: Thanks >>>>>> >>>>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2: >>>>>> >>>>>>> I spoke to soon. Adding the EmbeddedServletContainerConfig fixes >>>>>>> the serialization policy when running locally, but if you do a build >>>>>>> and >>>>>>> try to run. Ie: mvn clean package and then java -jar >>>>>>> myserver/myapp.war, >>>>>>> it crashes. >>>>>>> >>>>>>> I'll investigate. Any ideas/help most welcome. >>>>>>> >>>>>>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote: >>>>>>> >>>>>>>> > *New version available ... This one fixes the >>>>>>>> serializationPolicyFilePath issue ... * >>>>>>>> >>>>>>>> Awesome, thanks! I've closed >>>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 >>>>>>>> >>>>>>>> >>>>>>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: >>>>>>>> >>>>>>>>> Bott -> Boot ... (spelling correction arrrgh) >>>>>>>>> >>>>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/2b94c080-fe7f-4120-a1e7-4dd2a7286c5dn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Thanks for you PR. Your PR is merged and a new release is done. New version should be available soon. doing a `mvn clean compile` is usually enough to generate all necessary sources and run the project. It's much faster cause it avoids a GWT compile during build. In case you need a war, run `mvn clean verify`- not sure, if install is really needed. So, for develpment, `mvn clean compile` Is all you need to do. And it save a lot of time especially when the project gets more classes. Craig Mitchell schrieb am Montag, 20. Mai 2024 um 05:00:07 UTC+2: > Just tried a mvn install, and it seems to have worked. > > So I think the instructions > https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation > > : > cd gwt-maven-springboot-archetype && mvn clean compile > > should be: > cd gwt-maven-springboot-archetype && mvn clean install > > And my PR looks good. > > On Monday 20 May 2024 at 12:40:45 pm UTC+10 Craig Mitchell wrote: > >> Hi Frank. Unfortunately, that didn't work. I raised an issue: >> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15 >> >> I've also submitted a fix: >> https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16 >> >> However, I couldn't test my fix with the generation. The instructions >> here: >> https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation >> >> say to test, you do: >> >> cd gwt-maven-springboot-archetype && mvn clean compile >> >> And then I should be able to do: >> >> mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype >> -DarchetypeVersion=HEAD-SNAPSHOT >> -DarchetypeArtifactId=modular-springboot-webapp >> >> But that fails with: >> >> *The desired archetype does not exist >> (com:modular-springboot-webapp:HEAD-SNAPSHOT)* >> >> I suspect I'm supposed to do a mvn install? Or mvn deploy? Something >> that makes HEAD-SNAPSHOT available? >> >> On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote: >> >>> I'll added some additional code to avoid adding the launcherDir as >>> document root in production mode. >>> New version should be soon available. >>> >>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2: >>> >>>> The issue seems to be the launcherDir directory doesn't exist. I've >>>> raised a an issue with the full stack trace: >>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13 >>>> >>>> On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote: >>>> >>>>> please can you post the error message: Thanks >>>>> >>>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2: >>>>> >>>>>> I spoke to soon. Adding the EmbeddedServletContainerConfig fixes the >>>>>> serialization policy when running locally, but if you do a build and try >>>>>> to >>>>>> run. Ie: mvn clean package and then java -jar myserver/myapp.war, it >>>>>> crashes. >>>>>> >>>>>> I'll investigate. Any ideas/help most welcome. >>>>>> >>>>>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote: >>>>>> >>>>>>> > *New version available ... This one fixes the >>>>>>> serializationPolicyFilePath issue ... * >>>>>>> >>>>>>> Awesome, thanks! I've closed >>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 >>>>>>> >>>>>>> >>>>>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: >>>>>>> >>>>>>>> Bott -> Boot ... (spelling correction arrrgh) >>>>>>>> >>>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f140819d-acad-4b1e-b709-311f4ca3820cn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Thanks for you PR. Your PR is merged and a new release is done. New version should be available soon. doing a `mvn clean compile` is usually enough to generate all necessary sources and run the project. It's much faster cause it avoids a GWT compile during build. In cause you need a war, run `mvn clean verify`- not sure, if install is really needed. So, for develpment, `mvn clean compile` Is all you need to do. And it save a lot of time especially when the project gets more classes. Craig Mitchell schrieb am Montag, 20. Mai 2024 um 05:00:07 UTC+2: > Just tried a mvn install, and it seems to have worked. > > So I think the instructions > https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation > > : > cd gwt-maven-springboot-archetype && mvn clean compile > > should be: > cd gwt-maven-springboot-archetype && mvn clean install > > And my PR looks good. > > On Monday 20 May 2024 at 12:40:45 pm UTC+10 Craig Mitchell wrote: > >> Hi Frank. Unfortunately, that didn't work. I raised an issue: >> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15 >> >> I've also submitted a fix: >> https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16 >> >> However, I couldn't test my fix with the generation. The instructions >> here: >> https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation >> >> say to test, you do: >> >> cd gwt-maven-springboot-archetype && mvn clean compile >> >> And then I should be able to do: >> >> mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype >> -DarchetypeVersion=HEAD-SNAPSHOT >> -DarchetypeArtifactId=modular-springboot-webapp >> >> But that fails with: >> >> *The desired archetype does not exist >> (com:modular-springboot-webapp:HEAD-SNAPSHOT)* >> >> I suspect I'm supposed to do a mvn install? Or mvn deploy? Something >> that makes HEAD-SNAPSHOT available? >> >> On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote: >> >>> I'll added some additional code to avoid adding the launcherDir as >>> document root in production mode. >>> New version should be soon available. >>> >>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2: >>> >>>> The issue seems to be the launcherDir directory doesn't exist. I've >>>> raised a an issue with the full stack trace: >>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13 >>>> >>>> On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote: >>>> >>>>> please can you post the error message: Thanks >>>>> >>>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2: >>>>> >>>>>> I spoke to soon. Adding the EmbeddedServletContainerConfig fixes the >>>>>> serialization policy when running locally, but if you do a build and try >>>>>> to >>>>>> run. Ie: mvn clean package and then java -jar myserver/myapp.war, it >>>>>> crashes. >>>>>> >>>>>> I'll investigate. Any ideas/help most welcome. >>>>>> >>>>>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote: >>>>>> >>>>>>> > *New version available ... This one fixes the >>>>>>> serializationPolicyFilePath issue ... * >>>>>>> >>>>>>> Awesome, thanks! I've closed >>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 >>>>>>> >>>>>>> >>>>>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: >>>>>>> >>>>>>>> Bott -> Boot ... (spelling correction arrrgh) >>>>>>>> >>>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/9e22c73b-721b-49d4-8748-2d49f1986c4cn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Just tried a mvn install, and it seems to have worked. So I think the instructions https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation : cd gwt-maven-springboot-archetype && mvn clean compile should be: cd gwt-maven-springboot-archetype && mvn clean install And my PR looks good. On Monday 20 May 2024 at 12:40:45 pm UTC+10 Craig Mitchell wrote: > Hi Frank. Unfortunately, that didn't work. I raised an issue: > https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15 > > I've also submitted a fix: > https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16 > > However, I couldn't test my fix with the generation. The instructions > here: > https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation > > say to test, you do: > > cd gwt-maven-springboot-archetype && mvn clean compile > > And then I should be able to do: > > mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype > -DarchetypeVersion=HEAD-SNAPSHOT > -DarchetypeArtifactId=modular-springboot-webapp > > But that fails with: > > *The desired archetype does not exist > (com:modular-springboot-webapp:HEAD-SNAPSHOT)* > > I suspect I'm supposed to do a mvn install? Or mvn deploy? Something > that makes HEAD-SNAPSHOT available? > > On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote: > >> I'll added some additional code to avoid adding the launcherDir as >> document root in production mode. >> New version should be soon available. >> >> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2: >> >>> The issue seems to be the launcherDir directory doesn't exist. I've >>> raised a an issue with the full stack trace: >>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13 >>> >>> On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote: >>> >>>> please can you post the error message: Thanks >>>> >>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2: >>>> >>>>> I spoke to soon. Adding the EmbeddedServletContainerConfig fixes the >>>>> serialization policy when running locally, but if you do a build and try >>>>> to >>>>> run. Ie: mvn clean package and then java -jar myserver/myapp.war, it >>>>> crashes. >>>>> >>>>> I'll investigate. Any ideas/help most welcome. >>>>> >>>>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote: >>>>> >>>>>> > *New version available ... This one fixes the >>>>>> serializationPolicyFilePath issue ... * >>>>>> >>>>>> Awesome, thanks! I've closed >>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 >>>>>> >>>>>> >>>>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: >>>>>> >>>>>>> Bott -> Boot ... (spelling correction arrrgh) >>>>>>> >>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a1aff7cf-f86e-449c-a687-2bae830f828fn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Hi Frank. Unfortunately, that didn't work. I raised an issue: https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15 I've also submitted a fix: https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16 However, I couldn't test my fix with the generation. The instructions here: https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation say to test, you do: cd gwt-maven-springboot-archetype && mvn clean compile And then I should be able to do: mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype -DarchetypeVersion=HEAD-SNAPSHOT -DarchetypeArtifactId=modular-springboot-webapp But that fails with: *The desired archetype does not exist (com:modular-springboot-webapp:HEAD-SNAPSHOT)* I suspect I'm supposed to do a mvn install? Or mvn deploy? Something that makes HEAD-SNAPSHOT available? On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote: > I'll added some additional code to avoid adding the launcherDir as > document root in production mode. > New version should be soon available. > > Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2: > >> The issue seems to be the launcherDir directory doesn't exist. I've >> raised a an issue with the full stack trace: >> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13 >> >> On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote: >> >>> please can you post the error message: Thanks >>> >>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2: >>> >>>> I spoke to soon. Adding the EmbeddedServletContainerConfig fixes the >>>> serialization policy when running locally, but if you do a build and try >>>> to >>>> run. Ie: mvn clean package and then java -jar myserver/myapp.war, it >>>> crashes. >>>> >>>> I'll investigate. Any ideas/help most welcome. >>>> >>>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote: >>>> >>>>> > *New version available ... This one fixes the >>>>> serializationPolicyFilePath issue ... * >>>>> >>>>> Awesome, thanks! I've closed >>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 >>>>> >>>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: >>>>> >>>>>> Bott -> Boot ... (spelling correction arrrgh) >>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a05f1900-ba3e-447b-a056-c9fca4ccc5bbn%40googlegroups.com.
[ANN] JRS gwt-time 1.4.23/2.0.11 release
Hi, JRS gwt-time 1.4.23/2.0.11 has been released. - TZDB: 2024agtz - CLDR: v45 - Add Java 9 (partly) methods support. Details are on https://github.com/foal/gwt-time/releases/tag/v1.4.23 and https://github.com/foal/gwt-time/releases/tag/v2.0.11 Project page - https://github.com/foal/gwt-time Best, Stas -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/5fbe2a14-0e17-4b23-a870-a132267e28cdn%40googlegroups.com.
Re: [ANN] JRS gwt-time 1.4.22/2.0.10 release
New release with update TZDB is published to maven central Best, S. On Monday, April 8, 2024 at 8:15:54 PM UTC+2 Guillermo Hinojosa wrote: > Hi, > > I'm using gwt-time (great work by the way), and I noticed that the TZDB is > not updated for Mexico (two years ago Mexico stopped using DST). Is there a > way to manually update the TZDB? > > Thanks in advance. > > On Sunday, October 30, 2022 at 10:29:50 AM UTC-6 foal wrote: > >> Hi, >> >> JRS gwt-time 1.4.22/2.0.10 has been released. >> >> >>- TZDB 2022egtz >>- CLDR 42 >>- last updates from ThreeTen 1.6.3 release ( >>https://github.com/ThreeTen/threetenbp) merged. >> >> >> Details are on https://github.com/foal/gwt-time/releases/tag/v1.4.22 and >> https://github.com/foal/gwt-time/releases/tag/v2.0.10 >> >> Project page - https://github.com/foal/gwt-time >> >> Best, >> Stas >> > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/32e9c37b-67e6-4b80-9a5b-cfbd3289d0cbn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
I'll added some additional code to avoid adding the launcherDir as document root in production mode. New version should be soon available. Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2: > The issue seems to be the launcherDir directory doesn't exist. I've > raised a an issue with the full stack trace: > https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13 > > On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote: > >> please can you post the error message: Thanks >> >> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2: >> >>> I spoke to soon. Adding the EmbeddedServletContainerConfig fixes the >>> serialization policy when running locally, but if you do a build and try to >>> run. Ie: mvn clean package and then java -jar myserver/myapp.war, it >>> crashes. >>> >>> I'll investigate. Any ideas/help most welcome. >>> >>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote: >>> >>>> > *New version available ... This one fixes the >>>> serializationPolicyFilePath issue ... * >>>> >>>> Awesome, thanks! I've closed >>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 >>>> >>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: >>>> >>>>> Bott -> Boot ... (spelling correction arrrgh) >>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1f0480da-8548-4422-97c8-be1cce4a3839n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
The issue seems to be the launcherDir directory doesn't exist. I've raised a an issue with the full stack trace: https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13 On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote: > please can you post the error message: Thanks > > Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2: > >> I spoke to soon. Adding the EmbeddedServletContainerConfig fixes the >> serialization policy when running locally, but if you do a build and try to >> run. Ie: mvn clean package and then java -jar myserver/myapp.war, it >> crashes. >> >> I'll investigate. Any ideas/help most welcome. >> >> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote: >> >>> > *New version available ... This one fixes the >>> serializationPolicyFilePath issue ... * >>> >>> Awesome, thanks! I've closed >>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 >>> >>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: >>> >>>> Bott -> Boot ... (spelling correction arrrgh) >>>> >>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/caa4a474-3612-429c-a147-3bec9c788261n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
please can you post the error message: Thanks Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2: > I spoke to soon. Adding the EmbeddedServletContainerConfig fixes the > serialization policy when running locally, but if you do a build and try to > run. Ie: mvn clean package and then java -jar myserver/myapp.war, it > crashes. > > I'll investigate. Any ideas/help most welcome. > > On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote: > >> > *New version available ... This one fixes the >> serializationPolicyFilePath issue ... * >> >> Awesome, thanks! I've closed >> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 >> >> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: >> >>> Bott -> Boot ... (spelling correction arrrgh) >>> >>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6e0fb4be-406a-4b97-b8a4-7fcd71387bccn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
I spoke to soon. Adding the EmbeddedServletContainerConfig fixes the serialization policy when running locally, but if you do a build and try to run. Ie: mvn clean package and then java -jar myserver/myapp.war, it crashes. I'll investigate. Any ideas/help most welcome. On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote: > > *New version available ... This one fixes the > serializationPolicyFilePath issue ... * > > Awesome, thanks! I've closed > https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 > > On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: > >> Bott -> Boot ... (spelling correction arrrgh) >> >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/e8ecb6f8-fcdc-42f1-a94f-bdd42e50c9c0n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
> *New version available ... This one fixes the serializationPolicyFilePath issue ... * Awesome, thanks! I've closed https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7 On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote: > Bott -> Boot ... (spelling correction arrrgh) > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/59963153-ef79-41aa-bde8-6bfece30b30fn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Bott -> Boot ... (spelling correction arrrgh) -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/8726885d-cac3-43ff-8bc4-cc0353aeab44n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
and the version of Spring Bott is updated to 3.2.5 Frank Hossfeld schrieb am Mittwoch, 15. Mai 2024 um 20:36:10 UTC+2: > New version available ... This one fixes the serializationPolicyFilePath > issue ... > > Craig Mitchell schrieb am Montag, 4. März 2024 um 12:59:57 UTC+1: > >> Thank you Frank for making the excellent tool! Just checked the changes, >> working perfectly. >> >> On Monday 4 March 2024 at 7:55:58 pm UTC+11 Frank Hossfeld wrote: >> >>> Thanks Craig for contributing. New version is online. >>> >>> Frank Hossfeld schrieb am Dienstag, 6. Februar 2024 um 08:11:15 UTC+1: >>> >>>> new version is online ... >>>> >>>> Craig Mitchell schrieb am Montag, 5. Februar 2024 um 02:13:45 UTC+1: >>>> >>>>> Done: >>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/4 >>>>> Cheers. >>>>> >>>>> On Monday 5 February 2024 at 3:59:55 am UTC+11 Frank Hossfeld wrote: >>>>> >>>>>> Please can you open an issue regarding the gwt-servlet-jakarta >>>>>> problem ... >>>>>> >>>>>> Thanks >>>>>> >>>>>> Craig Mitchell schrieb am Sonntag, 4. Februar 2024 um 04:57:34 UTC+1: >>>>>> >>>>>>> I noticed that it always logs the error: >>>>>>> >>>>>>> ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not >>>>>>> found; did you forget to include it in this deployment? >>>>>>> >>>>>>> on the first RPC call. The RPC still seems to work fine, but >>>>>>> wondering if this is an issue or not? >>>>>>> >>>>>>> Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"? >>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16 >>>>>>> >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell >>>>>>> wrote: >>>>>>> >>>>>>>> Just realised you can also set it in your server pom.xml, in the >>>>>>>> Spring Boot Maven plugin (configuration > jvmArguments), instead of >>>>>>>> the >>>>>>>> launcher: >>>>>>>> >>>>>>>> >>>>>>>> org.springframework.boot >>>>>>>> spring-boot-maven-plugin >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> repackage >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> >>>>>>>> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote: >>>>>>>> >>>>>>>>> Thanks Thomas. Now switched to: >>>>>>>>> >>>>>>>>> >>>>>>>>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>>>>>>> >>>>>>>>> [image: Screen.png] >>>>>>>>> >>>>>>>>> Which also works great. >>>>>>>>> >>>>>>>>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) >>>>>>>>>> rather than the legacy -Xdebug -Xrunjdwp (and then you no longer >>>>>>>>>> need the >>>>>>>>>> quotes ) >>>>>>>>>> >>>>>>>>>> And when I say legacy, I really mean it: already in Java 8 >>>>>>>>>> -Xdebug does nothing ( >>>>>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) >>>>>>>>>> >>>>>>>>>> and Xrunjdwp is superceded by agentlib ( >>>>>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG >>>>>>>>>> ) >>>>>>>>>> >>>>>>>>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 >>>>>>>>>> ma...@craig-mitchell.com wrote: >>>>>>>>>> >>>>>>>>>>> Thank you! Working great now (quotes were important). >>>>>>>>>>> >>>>>>>>>>> [image: Screen.png] >>>>>>>>>>> >>>>>>>>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Mmmh, it might be worth adding this information to the >>>>>>>>>>>> archetype docs. >>>>>>>>>>>> >>>>>>>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/dbeab6cf-355f-46da-a67b-0035f8ae6c0an%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
New version available ... This one fixes the serializationPolicyFilePath issue ... Craig Mitchell schrieb am Montag, 4. März 2024 um 12:59:57 UTC+1: > Thank you Frank for making the excellent tool! Just checked the changes, > working perfectly. > > On Monday 4 March 2024 at 7:55:58 pm UTC+11 Frank Hossfeld wrote: > >> Thanks Craig for contributing. New version is online. >> >> Frank Hossfeld schrieb am Dienstag, 6. Februar 2024 um 08:11:15 UTC+1: >> >>> new version is online ... >>> >>> Craig Mitchell schrieb am Montag, 5. Februar 2024 um 02:13:45 UTC+1: >>> >>>> Done: >>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/4 >>>> Cheers. >>>> >>>> On Monday 5 February 2024 at 3:59:55 am UTC+11 Frank Hossfeld wrote: >>>> >>>>> Please can you open an issue regarding the gwt-servlet-jakarta problem >>>>> ... >>>>> >>>>> Thanks >>>>> >>>>> Craig Mitchell schrieb am Sonntag, 4. Februar 2024 um 04:57:34 UTC+1: >>>>> >>>>>> I noticed that it always logs the error: >>>>>> >>>>>> ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not >>>>>> found; did you forget to include it in this deployment? >>>>>> >>>>>> on the first RPC call. The RPC still seems to work fine, but >>>>>> wondering if this is an issue or not? >>>>>> >>>>>> Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"? >>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16 >>>>>> >>>>>> >>>>>> Thanks. >>>>>> >>>>>> On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell >>>>>> wrote: >>>>>> >>>>>>> Just realised you can also set it in your server pom.xml, in the >>>>>>> Spring Boot Maven plugin (configuration > jvmArguments), instead of the >>>>>>> launcher: >>>>>>> >>>>>>> >>>>>>> org.springframework.boot >>>>>>> spring-boot-maven-plugin >>>>>>> >>>>>>> >>>>>>> >>>>>>> repackage >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> false >>>>>>> >>>>>>> >>>>>>> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote: >>>>>>> >>>>>>>> Thanks Thomas. Now switched to: >>>>>>>> >>>>>>>> >>>>>>>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>>>>>> >>>>>>>> [image: Screen.png] >>>>>>>> >>>>>>>> Which also works great. >>>>>>>> >>>>>>>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer >>>>>>>> wrote: >>>>>>>> >>>>>>>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) >>>>>>>>> rather than the legacy -Xdebug -Xrunjdwp (and then you no longer need >>>>>>>>> the >>>>>>>>> quotes ) >>>>>>>>> >>>>>>>>> And when I say legacy, I really mean it: already in Java 8 -Xdebug >>>>>>>>> does nothing ( >>>>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) >>>>>>>>> >>>>>>>>> and Xrunjdwp is superceded by agentlib ( >>>>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG >>>>>>>>> ) >>>>>>>>> >>>>>>>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 >>>>>>>>> ma...@craig-mitchell.com wrote: >>>>>>>>> >>>>>>>>>> Thank you! Working great now (quotes were important). >>>>>>>>>> >>>>>>>>>> [image: Screen.png] >>>>>>>>>> >>>>>>>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Mmmh, it might be worth adding this information to the archetype >>>>>>>>>>> docs. >>>>>>>>>>> >>>>>>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/d6b24035-3b55-475c-b6ea-aafa47f69fd2n%40googlegroups.com.
Re: Unable to Access GWT CodeServer Outside of WSL Environment
I found that info after sending the reply. Thanks for your help!
On Thursday, May 9, 2024 at 9:15:13 AM UTC+2 Anders Kobberup wrote:
> Hi Craig
>
> That works - awesome!
> We have been using GWT since 2010 for our monolith of a project and have
> never found the need to change the maven plugin. Whats the improvements
> over the old plugin?
>
> Kind regards - and thanks again!
>
> /Anders
> On Thursday, May 9, 2024 at 6:02:22 AM UTC+2 Craig Mitchell wrote:
>
>> I haven't used that old plugin for awhile, but I think you need to set
>> the bindAddress to 0.0.0.0:
>> https://gwt-maven-plugin.github.io/gwt-maven-plugin/eclipse-mojo.html#bindAddress
>>
>> You might like to do a test with generating a sample app with
>> https://github.com/tbroyer/gwt-maven-archetypes which will use
>> https://github.com/tbroyer/gwt-maven-plugin instead, and see if that
>> works. More instructions here:
>> https://www.gwtproject.org/gettingstarted-v2.html
>>
>> On Thursday 9 May 2024 at 1:36:30 am UTC+10 Anders Kobberup wrote:
>>
>>> I am encountering an issue with accessing the GWT CodeServer from
>>> outside the Windows Subsystem for Linux (WSL) environment. I'm hoping to
>>> get some guidance or assistance on resolving this issue.
>>>
>>> The problem arises when attempting to access the GWT CodeServer running
>>> within the WSL environment from a browser outside of WSL.
>>> Specifically, I can access the GWT application's main page from my
>>> browser by navigating to localhost:8001, but I cannot connect to the
>>> CodeServer at http://localhost:8501.
>>>
>>> From within the WSL terminal i can telnet the port and it looks good,
>>> but i cannot from the outside host.
>>>
>>> My theory is that the codeserver only accepts connections from localhost
>>> - but i do not know how to set a host="0.0.0.0" or something like that on
>>> the jetty running the codeserver.
>>>
>>> We use the org.codehaus.mojo gwt-maven-plugin with these settings:
>>>
>>> org.codehaus.mojo
>>> gwt-maven-plugin
>>> 2.10.0
>>>
>>> 1
>>> true
>>> true
>>> true
>>> false
>>> INFO
>>> OBF
>>> auto
>>> -Xmx7G --add-opens
>>> java.base/java.lang=ALL-UNNAMED
>>>
>>> com.toh.manager.ManagerclientDev
>>> true
>>> 8001
>>> 8010
>>> 8501
>>> managerclient.html
>>> ${project.basedir}/src/main/webapp
>>> true
>>>
>>> /tmp/gwt-${project.build.finalName}
>>>
>>>
>>>
>>> Please let me know if you need anymore information
>>>
>>>
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/4774b340-142b-4e21-a305-fe016e9567b0n%40googlegroups.com.
Re: Unable to Access GWT CodeServer Outside of WSL Environment
Hi Craig
That works - awesome!
We have been using GWT since 2010 for our monolith of a project and have
never found the need to change the maven plugin. Whats the improvements
over the old plugin?
Kind regards - and thanks again!
/Anders
On Thursday, May 9, 2024 at 6:02:22 AM UTC+2 Craig Mitchell wrote:
> I haven't used that old plugin for awhile, but I think you need to set
> the bindAddress to 0.0.0.0:
> https://gwt-maven-plugin.github.io/gwt-maven-plugin/eclipse-mojo.html#bindAddress
>
> You might like to do a test with generating a sample app with
> https://github.com/tbroyer/gwt-maven-archetypes which will use
> https://github.com/tbroyer/gwt-maven-plugin instead, and see if that
> works. More instructions here:
> https://www.gwtproject.org/gettingstarted-v2.html
>
> On Thursday 9 May 2024 at 1:36:30 am UTC+10 Anders Kobberup wrote:
>
>> I am encountering an issue with accessing the GWT CodeServer from outside
>> the Windows Subsystem for Linux (WSL) environment. I'm hoping to get some
>> guidance or assistance on resolving this issue.
>>
>> The problem arises when attempting to access the GWT CodeServer running
>> within the WSL environment from a browser outside of WSL.
>> Specifically, I can access the GWT application's main page from my
>> browser by navigating to localhost:8001, but I cannot connect to the
>> CodeServer at http://localhost:8501.
>>
>> From within the WSL terminal i can telnet the port and it looks good, but
>> i cannot from the outside host.
>>
>> My theory is that the codeserver only accepts connections from localhost
>> - but i do not know how to set a host="0.0.0.0" or something like that on
>> the jetty running the codeserver.
>>
>> We use the org.codehaus.mojo gwt-maven-plugin with these settings:
>>
>> org.codehaus.mojo
>> gwt-maven-plugin
>> 2.10.0
>>
>> 1
>> true
>> true
>> true
>> false
>> INFO
>> OBF
>> auto
>> -Xmx7G --add-opens
>> java.base/java.lang=ALL-UNNAMED
>>
>> com.toh.manager.ManagerclientDev
>> true
>> 8001
>> 8010
>> 8501
>> managerclient.html
>> ${project.basedir}/src/main/webapp
>> true
>>
>> /tmp/gwt-${project.build.finalName}
>>
>>
>>
>> Please let me know if you need anymore information
>>
>>
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/4de1ff5d-d008-4b64-bc46-f71f58c14040n%40googlegroups.com.
Re: Unable to Access GWT CodeServer Outside of WSL Environment
I haven't used that old plugin for awhile, but I think you need to set the
bindAddress to
0.0.0.0:
https://gwt-maven-plugin.github.io/gwt-maven-plugin/eclipse-mojo.html#bindAddress
You might like to do a test with generating a sample app
with https://github.com/tbroyer/gwt-maven-archetypes which will use
https://github.com/tbroyer/gwt-maven-plugin instead, and see if that
works. More instructions
here: https://www.gwtproject.org/gettingstarted-v2.html
On Thursday 9 May 2024 at 1:36:30 am UTC+10 Anders Kobberup wrote:
> I am encountering an issue with accessing the GWT CodeServer from outside
> the Windows Subsystem for Linux (WSL) environment. I'm hoping to get some
> guidance or assistance on resolving this issue.
>
> The problem arises when attempting to access the GWT CodeServer running
> within the WSL environment from a browser outside of WSL.
> Specifically, I can access the GWT application's main page from my browser
> by navigating to localhost:8001, but I cannot connect to the CodeServer
> at http://localhost:8501.
>
> From within the WSL terminal i can telnet the port and it looks good, but
> i cannot from the outside host.
>
> My theory is that the codeserver only accepts connections from localhost -
> but i do not know how to set a host="0.0.0.0" or something like that on the
> jetty running the codeserver.
>
> We use the org.codehaus.mojo gwt-maven-plugin with these settings:
>
> org.codehaus.mojo
> gwt-maven-plugin
> 2.10.0
>
> 1
> true
> true
> true
> false
> INFO
> OBF
> auto
> -Xmx7G --add-opens
> java.base/java.lang=ALL-UNNAMED
>
> com.toh.manager.ManagerclientDev
> true
> 8001
> 8010
> 8501
> managerclient.html
> ${project.basedir}/src/main/webapp
> true
>
> /tmp/gwt-${project.build.finalName}
>
>
>
> Please let me know if you need anymore information
>
>
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/d4bfca14-1d70-4b0e-b09e-964fa8568caan%40googlegroups.com.
Unable to Access GWT CodeServer Outside of WSL Environment
I am encountering an issue with accessing the GWT CodeServer from outside
the Windows Subsystem for Linux (WSL) environment. I'm hoping to get some
guidance or assistance on resolving this issue.
The problem arises when attempting to access the GWT CodeServer running
within the WSL environment from a browser outside of WSL.
Specifically, I can access the GWT application's main page from my browser
by navigating to localhost:8001, but I cannot connect to the CodeServer at
http://localhost:8501.
>From within the WSL terminal i can telnet the port and it looks good, but i
cannot from the outside host.
My theory is that the codeserver only accepts connections from localhost -
but i do not know how to set a host="0.0.0.0" or something like that on the
jetty running the codeserver.
We use the org.codehaus.mojo gwt-maven-plugin with these settings:
org.codehaus.mojo
gwt-maven-plugin
2.10.0
1
true
true
true
false
INFO
OBF
auto
-Xmx7G --add-opens
java.base/java.lang=ALL-UNNAMED
com.toh.manager.ManagerclientDev
true
8001
8010
8501
managerclient.html
${project.basedir}/src/main/webapp
true
/tmp/gwt-${project.build.finalName}
Please let me know if you need anymore information
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/50809691-427f-40e1-b492-b576bfe1e17en%40googlegroups.com.
[gwt-contrib] Re: Seeking Advice on Legacy Application Migration Strategy
Then the very first thing to do is stop using the embedded Jetty of GWT DevMode as application server. The embedded Jetty in GWT DevMode does some ClassLoader hacks and it often causes issues for people using the embedded Jetty as application server. That is the reason why GWT 2.11 has deprecated the use of embedded Jetty except for demo purposes. If you search for "jetty-web.xml" or "jetty-env.xml" on Github GWT issues then you will already find some issues with the above stack trace. So you should find a solution to run a dedicated servlet container (jetty, tomcat, etc) that fits your workflow. GWT has updated its Getting Started instructions (https://www.gwtproject.org/gettingstarted-v2.html) to use the recommended project layout and a dedicated servlet container via Maven plugin. The core essence is to split the legacy project layout into three projects (client, shared, server) with dedicated classpaths and use a build tool to build a *.war file (or an exploded war folder) and then deploy this file/folder to a dedicated servlet container of your choice. The dedicated servlet container can then be configured as you like, usually as closely to your production server as possible. Personally I don't like launching a servlet container via a build tool so I use a jetty docker container and a shell script to deploy the webapp. -- J. Wejden Mrabti schrieb am Mittwoch, 1. Mai 2024 um 17:09:57 UTC+2: > > thank you @jens for your answer > > I started by upgrading gwt Only from version 2.8.2 To 2.10.0 and I kept > java 8 . > I my jetty-env.xml file i had org.eclipse.jetty.webapp.WebAppContext as > a configurationClass, so It cause fd ollowing error when launching > java.lang.ClassNotFoundException: > org.eclipse.jetty.webapp.WebAppContext > at java.lang.ClassLoader.findClass(ClassLoader.java:523) > at java.lang.ClassLoader.loadClass(ClassLoader.java:418) > at java.lang.ClassLoader.loadClass(ClassLoader.java:351) > at > org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:487) > at > com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload$WebAppClassLoaderExtension.loadClass(JettyLauncher.java:458) > at java.lang.ClassLoader.loadClass(ClassLoader.java:351) > at org.eclipse.jetty.util.Loader.loadClass(Loader.java:64) > at > org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.nodeClass(XmlConfiguration.java:477) > at > org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:417) > at > org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:364) > at > org.eclipse.jetty.plus.webapp.EnvConfiguration.lambda$configure$0(EnvConfiguration.java:120) > at > org.eclipse.jetty.webapp.WebAppClassLoader.runWithServerClassAccess(WebAppClassLoader.java:138) > at > org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:118) > at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:498) > at > org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1409) > at > org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:910) > at > org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288) > at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524) > at > com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:568) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) > at > org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) > at org.eclipse.jetty.server.Server.start(Server.java:423) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) > at > org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) > at org.eclipse.jetty.server.Server.doStart(Server.java:387) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) > at > com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:776) > at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636) > at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:898) > at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:705) > at com.google.gwt.dev.DevMode.main(DevMode.java:432) > Suppressed: java.l
[gwt-contrib] Re: Seeking Advice on Legacy Application Migration Strategy
thank you @jens for your answer I started by upgrading gwt Only from version 2.8.2 To 2.10.0 and I kept java 8 . I my jetty-env.xml file i had org.eclipse.jetty.webapp.WebAppContext as a configurationClass, so It cause fd ollowing error when launching java.lang.ClassNotFoundException: org.eclipse.jetty.webapp.WebAppContext at java.lang.ClassLoader.findClass(ClassLoader.java:523) at java.lang.ClassLoader.loadClass(ClassLoader.java:418) at java.lang.ClassLoader.loadClass(ClassLoader.java:351) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:487) at com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload$WebAppClassLoaderExtension.loadClass(JettyLauncher.java:458) at java.lang.ClassLoader.loadClass(ClassLoader.java:351) at org.eclipse.jetty.util.Loader.loadClass(Loader.java:64) at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.nodeClass(XmlConfiguration.java:477) at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:417) at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:364) at org.eclipse.jetty.plus.webapp.EnvConfiguration.lambda$configure$0(EnvConfiguration.java:120) at org.eclipse.jetty.webapp.WebAppClassLoader.runWithServerClassAccess(WebAppClassLoader.java:138) at org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:118) at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:498) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1409) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:910) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524) at com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:568) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) at org.eclipse.jetty.server.Server.start(Server.java:423) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) at org.eclipse.jetty.server.Server.doStart(Server.java:387) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:776) at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636) at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:898) at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:705) at com.google.gwt.dev.DevMode.main(DevMode.java:432) Suppressed: java.lang.ClassNotFoundException: org.eclipse.jetty.webapp.WebAppContext at java.net.URLClassLoader.findClass(URLClassLoader.java:387) at org.eclipse.jetty.webapp.WebAppClassLoader.findClass(WebAppClassLoader.java:629) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:511) ... 31 more Le mardi 30 avril 2024 à 10:37:22 UTC+2, Jens a écrit : > I would first focus on upgrading Java, GWT and possibly GXT if it is > incompatible with newest GWT. The DataSource error will go away once you > upgrade GWT because newer GWT versions use a newer Jetty. Keep in mind that > in newest GWT the use of embedded Jetty as appliction server during > development has been deprecated. It is preferred to use a local jetty > installation, a docker container or launching jetty via a build tool plugin > (maven / gradle). > > Once you have upgraded to latest GWT you have the possibility to use GWT > 2.11-jakarta if you need to switch to Jakarta. > > GWT itself only supports Hibernate 4 validation. So if the application > uses Hibernate validation in GWT as well, then you likely need to use > https://gitlab.com/ManfredTremmel/gwt-bean-validators > > -- J. > > Wejden Mrabti schrieb am Donnerstag, 25. April 2024 um 15:59:45 UTC+2: > >> Hello GWT Community, >> >> I'm currently working on a large legacy application stack, using Java 8, >> Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our >> frontend technology stack includes GWT version 2.8.2 and GXT version >> 2.3.1a-gwt22. Fontend and backend arent well de-coupled. >> >> In my initial approach to modernize the application, I began by migrating >> Hibernate to version 6.2, assuming it would
[gwt-contrib] Re: Seeking Advice on Legacy Application Migration Strategy
I would first focus on upgrading Java, GWT and possibly GXT if it is incompatible with newest GWT. The DataSource error will go away once you upgrade GWT because newer GWT versions use a newer Jetty. Keep in mind that in newest GWT the use of embedded Jetty as appliction server during development has been deprecated. It is preferred to use a local jetty installation, a docker container or launching jetty via a build tool plugin (maven / gradle). Once you have upgraded to latest GWT you have the possibility to use GWT 2.11-jakarta if you need to switch to Jakarta. GWT itself only supports Hibernate 4 validation. So if the application uses Hibernate validation in GWT as well, then you likely need to use https://gitlab.com/ManfredTremmel/gwt-bean-validators -- J. Wejden Mrabti schrieb am Donnerstag, 25. April 2024 um 15:59:45 UTC+2: > Hello GWT Community, > > I'm currently working on a large legacy application stack, using Java 8, > Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our > frontend technology stack includes GWT version 2.8.2 and GXT version > 2.3.1a-gwt22. Fontend and backend arent well de-coupled. > > In my initial approach to modernize the application, I began by migrating > Hibernate to version 6.2, assuming it would be the easiest step. However, I > encountered an issue where Hibernate 6.2 requires transitioning to Jakarta > Persistence. When attempting to compile parts of my codebase, I received > the following error: > > java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient has > been compiled by a more recent version of the Java Runtime (class file > version 55.0), this version of the Java Runtime only recognizes class file > versions up to 52.0 > > This suggests that I need to execute my code with JDK 11. However, when > attempting to do so, I encountered the following issue: > > [ERROR] Found resouce but unrecognized URL format: > 'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError: > javax/sql/DataSource > > After reviewing your discussions in the GWT contributors group, I'm > questioning whether starting with the Hibernate migration is the right > approach. Should I instead prioritize migrating Java or perhaps GWT? I > would greatly appreciate your insights and advice based on your experiences. > > Thank you, > > WM > -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/d52d9aa6-5cc0-4f5b-be14-907bf758d2ecn%40googlegroups.com.
[gwt-contrib] Seeking Advice on Legacy Application Migration Strategy
Hello GWT Community, I'm currently working on a large legacy application stack, using Java 8, Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our frontend technology stack includes GWT version 2.8.2 and GXT version 2.3.1a-gwt22. Fontend and backend arent well de-coupled. In my initial approach to modernize the application, I began by migrating Hibernate to version 6.2, assuming it would be the easiest step. However, I encountered an issue where Hibernate 6.2 requires transitioning to Jakarta Persistence. When attempting to compile parts of my codebase, I received the following error: java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 This suggests that I need to execute my code with JDK 11. However, when attempting to do so, I encountered the following issue: [ERROR] Found resouce but unrecognized URL format: 'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError: javax/sql/DataSource After reviewing your discussions in the GWT contributors group, I'm questioning whether starting with the Hibernate migration is the right approach. Should I instead prioritize migrating Java or perhaps GWT? I would greatly appreciate your insights and advice based on your experiences. Thank you, WM -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/1ab55db1-72aa-423d-9b06-c238993208fdn%40googlegroups.com.
Re: Really need help getting CodeServer to run with Java 11 and GWT 2.10
Note sure if this will gelp you much - we're a Gradle user, and don't use
intellij. But the basic principles are the same.
When we migrated to the latest GWT we also updated our top level gradle
build file to have a gwtSuperDev task which does all the heavy lifting for
us:
task gwtSuperDev(dependsOn: 'build') {
// probably a nicer way of getting these (e.g through project
sourcepaths)
def gwtapi_src = file('tas/gwtapi/src')
def webui_src = file('webui/src')
doLast {
def compilerArgs = [
"-strict", "-noincremental", "-noprecompile",
"-src", "${gwtapi_src}/",
"-src", "${webui_src}/",
"com.ascert.webui.vt.VtWebUi-dev"
]
javaexec {
main = 'com.google.gwt.dev.codeserver.CodeServer'
// Leverage the Gradle create classpaths for gwtapi and
webui subprojects
// Make sure GWT build libs are at the front to ensure the
vanilla GWT jetty classes are used by codeserver
classpath += configurations.gwtBuild
// These classpaths will duplicate some of the above, but
doing this way ensures our custom jetty does not get
// picked up by GWT codeserver, which causes class
inconsistencies.
classpath +=
project(':proj:webui').configurations.compileClasspath
classpath +=
project(':proj:tas:gwtapi').configurations.compileClasspath
maxHeapSize = "1000m"
args = compilerArgs.flatten()
}
}
}
Our 2 main source trees are defined by gwtapi_src and webui_src. The
com.ascert.webui.vt.VtWebUi-dev
is our dev GWT XML file name. It's slightly different to our prod one as it
has debug flags on and only creates a single large permutation.
That's really the main part. We also have the source modules on the
classpath as :proj:webui and :proj:gwtapi - for reasons as per the comments.
The only other crucial part is the configurations.gwtBuild. This is a
gradle configuration with all the JARs needed for codeserver (gwt_dev,
gwt_user, various js lib jars such as GXT etc.). It's really just a
convenient way of handling classpath JARs and nothing more. If/when we
update the versions of any of those, the above automatically pulls in the
updated dependency versions.
There's really nothing that special about CodeServer apart from making sure
all your own sources and JARs are on the classpath, plus the standard GWT
ones and any 3rd party libs you use. Although the above is for Gradle, the
same principles and approach ought to apply for MVN or any other build tool.
Good luck!
-Rob
On Monday 15 April 2024 at 10:13:19 UTC+1 Mathias wrote:
> Hi Thomas
>
> unfortunately, I'm still stuck. I thought I'd attack the Lombok dependency
> first, since that's a third-party it depends on. I don't suppose you've
> ever been exposed to that?
> I tried setting the
> *compile *to the "configuration" setting
> of the plugin def in pluginmanagement of the root pom. That didn't help.
> (neither compile+runtime)
>
> In the intellij GWT-plugin I got it working while running by setting the
> argument "-javaagent:/...path/lombok-1.16.14.jar=ECJ , not sure if that
> could change anything. I mean this breaks at compile so I don't know.
>
> I have gone through the configuration line-by line with both your
> archetype project and the NaluKit Marco tipped me about. I can't see any
> relevant difference. I don't have *gwt-lib *on any
> dependency, but neither does any of the other projects I look at.
>
> I also tried adding lombok dependency to the plugin, it didn't help either.
>
> I am basically stuck, this is not great. Would you have time to look at
> the plugin config if I pasted it?
>
> On Friday 12 April 2024 at 11:20:01 UTC+2 Thomas Broyer wrote:
>
>> On Friday, April 12, 2024 at 7:50:42 AM UTC+2 Mathias wrote:
>>
>> -My dependencies should be ok since i can build it with the plugin, so
>> i'm a bit at a loss as to how make this work.
>>
>>
>> Dependencies for gwt:compile and gwt:codeserver aren't the same:
>> https://tbroyer.github.io/gwt-maven-plugin/codeserver.html
>> You might have to either adjust the of dependencies (e.g. from
>> provided to compile) or adjust the gwt:codeserver's classpathScope (e.g.
>> from runtime to compile+runtime or compile)
>>
>>
>> as a final aside:
>> The "neither a gwt-lib or jar" warning messages in the error log below -
>> i still get it if i add the gwt-lib type to the dependency, and the
>> archetype project print
Re: Really need help getting CodeServer to run with Java 11 and GWT 2.10
Hi Thomas unfortunately, I'm still stuck. I thought I'd attack the Lombok dependency first, since that's a third-party it depends on. I don't suppose you've ever been exposed to that? I tried setting the *compile *to the "configuration" setting of the plugin def in pluginmanagement of the root pom. That didn't help. (neither compile+runtime) In the intellij GWT-plugin I got it working while running by setting the argument "-javaagent:/...path/lombok-1.16.14.jar=ECJ , not sure if that could change anything. I mean this breaks at compile so I don't know. I have gone through the configuration line-by line with both your archetype project and the NaluKit Marco tipped me about. I can't see any relevant difference. I don't have *gwt-lib *on any dependency, but neither does any of the other projects I look at. I also tried adding lombok dependency to the plugin, it didn't help either. I am basically stuck, this is not great. Would you have time to look at the plugin config if I pasted it? On Friday 12 April 2024 at 11:20:01 UTC+2 Thomas Broyer wrote: > On Friday, April 12, 2024 at 7:50:42 AM UTC+2 Mathias wrote: > > -My dependencies should be ok since i can build it with the plugin, so i'm > a bit at a loss as to how make this work. > > > Dependencies for gwt:compile and gwt:codeserver aren't the same: > https://tbroyer.github.io/gwt-maven-plugin/codeserver.html > You might have to either adjust the of dependencies (e.g. from > provided to compile) or adjust the gwt:codeserver's classpathScope (e.g. > from runtime to compile+runtime or compile) > > > as a final aside: > The "neither a gwt-lib or jar" warning messages in the error log below - i > still get it if i add the gwt-lib type to the dependency, and the archetype > project prints the same error when created. > > > Note that it's an info, not a warning > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/7ae59c63-c4a1-44a2-8d96-f1734a52708cn%40googlegroups.com.
Re: Problems moving JsInterop from GWT 2.7 to 2.8
" I also solved the problem of List and Map with an own Interface, which is
an ArrayList/HashMap on serverside and an own implemented native List/Map
on gwt side" can you share the solution ?
Il giorno venerdì 29 settembre 2017 alle 14:00:12 UTC+2 Ignacio Baca
Moreno-Torres ha scritto:
> We have been using this technique for more than a year and it works
> perfectly. We call it "Java Notation Object", hehe and you should
> understand the limitations, which more or less you are currently
> fulfilling. Just a few changes...
>
> The most important, yes, you should use
> @JsType(isNative=true,namespace=GLOBAL,name="Object"), so you are actually
> ignoring any kind of typing, so this is more a "scheme" of where to find
> things than an actual typed object. This is pretty important! This is
> pretty similar to JSON but in Java, and these classes are not actually Java
> classes, are just a scheme. All these limitations are the common
> intersection of the feature between Java and JS.
>
> You can do some tricks to use collections but we end up removing all of
> them and using arrays instead. But, to make it easy to work with, we added
> some @JsOverlay to return or set the Collection. For example if you have
> "String[] roles" you can add "@JsOverlay getRoleSet() { return
> Stream.of(roles).collecto(toSet()); }". Overlays are ok bc there are just
> like extension method or static method, so no behavior is added to the
> object.
>
> This work perfectly on both sides, but there is a small annoying
> difference between GWT and Java, in java new Foo() will initialize
> primitive types and in GWT (js) will not. So we never use constructor
> directly, in the kind of classes we always add a static factory method and
> we initialize any non-nullable field, even primitives! So in java you are
> actually creating the object of the specified type, but in JS you are just
> calling "new Object()", but it is ok, bc where are using a scheme, no a
> type. And we never use instanceof on these schemes! This will work on the
> Java side, but I strongly discourage, you should not need to do that.
>
> Finally, we never use getter and setter, don't make sense, you "cannot use
> inheritance" (you can use with some ticks too, for example using some int
> or string field as the type indicator and using, for example, the visitor
> pattern to traverse, this is what actually people need to do in JS so, no
> magic just the common intersection of features between java and json),
> almost everything is like final and you must not add behavior, so it is
> much explicit and easier to just make all field public.
>
> I think the first you should do is removing getters and setters, and add
> @JsType(native,Object) to all your types, this refactor can be done almost
> instantly in your IDE (inline method). Then stop using Collection might not
> be so easy to refactor. So you might continue using it either using
> overlays or creating a custom jsinterop-compatible type. In this case, I
> recommend to not to use the whole java.util API bc it will force you to
> export the whole API and use generateJsInteropExports. If you are really
> interested or need help there just ask, but just try out avoiding maps, and
> using arrays. Anyways, the "Map/List own interface" should work too, just
> neet to make it work.
>
> On Fri, Sep 29, 2017 at 12:53 PM Thomas Broyer wrote:
>
>>
>>
>> On Friday, September 29, 2017 at 11:09:42 AM UTC+2, Jürgen Beringer wrote:
>>>
>>> Hey,
>>>
>>> currently I tried the 2. time to move our application from gwt 2.7 to
>>> gwt 2.8, but I have big problems with the changes of JsInterop.
>>>
>>> The application contains a serverside java part, running in a jetty and
>>> the client part, build with gwt, so I can reuse many software on server and
>>> client side. (It is the main part of the website www.spreadshirt.com )
>>> To use also the same data classes (containing only fields with getter
>>> and setter, no other methods) on both sides, I used JsInterop and it works
>>> very well with gwt 2.7 and exchanged the data as json.
>>>
>>> Example Data class:
>>>
>>> @JsType
>>> public class MyObject {
>>> private String id;
>>>
>>> @JsProperty
>>> public String getId() {
>>> return id;
>>> }
>>> @JsProperty
>>> public void setId(String id) {
>>> this.id = id;
>>> }
>>> }
>>>
>>>
>>> The class can be used on s
Re: Really need help getting CodeServer to run with Java 11 and GWT 2.10
Thomas, Marco showed me a project that made me see one thing I hadn't thought about, which was configured the same in the archetype project. It's regarding the sources. In my project, I only have one jar that contain both classes and source files for those jar files that are needed, i.e. no sources-jar anywhere. This was a long time ago, but I think it was because we also needed to include things like .properties-files for i18n which are in submodules as well, so we use the tags to define them. In any case - this apparently works fine for the compile, but could this be a reason for CodeServer not finding the class files? On the other hand, it doesn't find Lombok either which worked before, and I don't have any lombok sources.jar in my repo. Perhaps it doesn't need the Lombok sources since it's just annotations? On Friday 12 April 2024 at 11:20:01 UTC+2 Thomas Broyer wrote: > On Friday, April 12, 2024 at 7:50:42 AM UTC+2 Mathias wrote: > > -My dependencies should be ok since i can build it with the plugin, so i'm > a bit at a loss as to how make this work. > > > Dependencies for gwt:compile and gwt:codeserver aren't the same: > https://tbroyer.github.io/gwt-maven-plugin/codeserver.html > You might have to either adjust the of dependencies (e.g. from > provided to compile) or adjust the gwt:codeserver's classpathScope (e.g. > from runtime to compile+runtime or compile) > > > as a final aside: > The "neither a gwt-lib or jar" warning messages in the error log below - i > still get it if i add the gwt-lib type to the dependency, and the archetype > project prints the same error when created. > > > Note that it's an info, not a warning > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a1d39578-5eff-4ede-9e2f-12d73422c98en%40googlegroups.com.
Re: Really need help getting CodeServer to run with Java 11 and GWT 2.10
Thanks! That's a great resource and got me to see one thing I'd missed. On Friday 12 April 2024 at 15:11:45 UTC+2 Marco Tenti (IoProgrammo88) wrote: > This project has many good examples to check out > https://github.com/NaluKit/nalu-examples, it help me a lot. > > Il giorno venerdì 12 aprile 2024 alle 14:39:16 UTC+2 Mathias ha scritto: > >> Hey Jens, thanks for replying! >> >> re. the gwt-type: >> >> 1. I only have one maven module that contains the entry point. the "gwt >> client" module >> 2. All dependencies are either on third-party such as Lombok, or my own >> other modules that only contain java classes and are built as jar-files. >> 3. I added the "type" gwt-lib to the dependencies in the "gwt client" >> pom, but I didn't do anything to the pom files in the jar modules that the >> gwt client depend on. I mean, Lombok doesn't have a packaging >> gwt-lib in its pom, either. >> >> On Friday 12 April 2024 at 11:15:38 UTC+2 Jens wrote: >> >>> A full example for multiple maven modules (more than just three) can be >>> found here: >>> https://github.com/tbroyer/gwt-maven-plugin/tree/main/src/it/e2e >>> >>> You have to add gwt-lib to your own maven library >>> modules that contain a module.gwt.xml file. Maybe you forgot that? >>> >>> -- J. >>> >>> Mathias schrieb am Freitag, 12. April 2024 um 07:50:42 UTC+2: >>> >>>> I *really* could use some help getting my project up for development >>>> after moving to gwt 2.10 and Java 11. >>>> I can unfortunately nolonger use the GWT intellij plugin i've loved and >>>> used for 12 years apparently, and i'm struggling a bit to get the >>>> codeserver running for my project. >>>> >>>> *CURRENT STATUS:* >>>> My project is over 12 years, but i migrated it from the old gwt mojo >>>> plugin to the new tbroyer one last year. >>>> It builds into a war fine and deploys on tomcat. Prior to the migration >>>> to GWT 2.10 (with new Jetty) and Java 11, i could run it with the GWT >>>> Intellij plugin, which I've loved and used for those same 12 years. >>>> But now the plugin unfortunately doesn't work, and from what I can tell >>>> due to the JettyLauncher, (I get lots of classnotfounds for for example >>>> javax.sql.DataSource) it's kind of impossible to make it run? So I >>>> thought >>>> I'd try what people have been saying, move to the manual thing with server >>>> and code server, even though it's a more cumbersome setup. >>>> >>>> As part of trying to get this show on the road, i created an archetype >>>> project and got codeserver and server running according to the new v2 >>>> tutorial. This works fine. >>>> >>>> *PROBLEM:* >>>> Basically i can't get the codeserver to run. My project is pretty large >>>> so my "webclient" module that contains my gwt client has a bunch of >>>> dependencies on my own child modules, and a couple of third-party ones >>>> such >>>> as Lombok. >>>> >>>> >>>> When i try the codeserver with this command (from the tutorial) >>>> * mvn gwt:codeserver -pl webclient -am* >>>> >>>> ,where the webclient is the module containing the gwt code and entry >>>> point, standing in the root dir of my project, >>>> ,i get page up and page down filled with missing dependencies from >>>> stuff and "did you forget to inherit"-errors. (see error extract at the >>>> bottom) >>>> >>>> -I'm not sure if this has something to do with the "workdir", the >>>> directory i stand in when i try to start the codeserver as described >>>> above, >>>> some dependency declaration i'm missing or something else. >>>> >>>> -My dependencies should be ok since i can build it with the plugin, so >>>> i'm a bit at a loss as to how make this work. >>>> >>>> -Help would be much appreciated, right now i can't develop and rolling >>>> our project back to 2.8 and Java 8 wouldn't be great and take time. Man >>>> how >>>> I wish that the intellij plugin had just kept working. >>>> >>>> as a final aside: >>>> The "neither a gwt-lib or jar" warning messages in the error log below >>>> - i still get it if i add the gwt-l
Re: Really need help getting CodeServer to run with Java 11 and GWT 2.10
This project has many good examples to check out https://github.com/NaluKit/nalu-examples, it help me a lot. Il giorno venerdì 12 aprile 2024 alle 14:39:16 UTC+2 Mathias ha scritto: > Hey Jens, thanks for replying! > > re. the gwt-type: > > 1. I only have one maven module that contains the entry point. the "gwt > client" module > 2. All dependencies are either on third-party such as Lombok, or my own > other modules that only contain java classes and are built as jar-files. > 3. I added the "type" gwt-lib to the dependencies in the "gwt client" pom, > but I didn't do anything to the pom files in the jar modules that the gwt > client depend on. I mean, Lombok doesn't have a packaging > gwt-lib in its pom, either. > > On Friday 12 April 2024 at 11:15:38 UTC+2 Jens wrote: > >> A full example for multiple maven modules (more than just three) can be >> found here: >> https://github.com/tbroyer/gwt-maven-plugin/tree/main/src/it/e2e >> >> You have to add gwt-lib to your own maven library >> modules that contain a module.gwt.xml file. Maybe you forgot that? >> >> -- J. >> >> Mathias schrieb am Freitag, 12. April 2024 um 07:50:42 UTC+2: >> >>> I *really* could use some help getting my project up for development >>> after moving to gwt 2.10 and Java 11. >>> I can unfortunately nolonger use the GWT intellij plugin i've loved and >>> used for 12 years apparently, and i'm struggling a bit to get the >>> codeserver running for my project. >>> >>> *CURRENT STATUS:* >>> My project is over 12 years, but i migrated it from the old gwt mojo >>> plugin to the new tbroyer one last year. >>> It builds into a war fine and deploys on tomcat. Prior to the migration >>> to GWT 2.10 (with new Jetty) and Java 11, i could run it with the GWT >>> Intellij plugin, which I've loved and used for those same 12 years. >>> But now the plugin unfortunately doesn't work, and from what I can tell >>> due to the JettyLauncher, (I get lots of classnotfounds for for example >>> javax.sql.DataSource) it's kind of impossible to make it run? So I thought >>> I'd try what people have been saying, move to the manual thing with server >>> and code server, even though it's a more cumbersome setup. >>> >>> As part of trying to get this show on the road, i created an archetype >>> project and got codeserver and server running according to the new v2 >>> tutorial. This works fine. >>> >>> *PROBLEM:* >>> Basically i can't get the codeserver to run. My project is pretty large >>> so my "webclient" module that contains my gwt client has a bunch of >>> dependencies on my own child modules, and a couple of third-party ones such >>> as Lombok. >>> >>> >>> When i try the codeserver with this command (from the tutorial) >>> * mvn gwt:codeserver -pl webclient -am* >>> >>> ,where the webclient is the module containing the gwt code and entry >>> point, standing in the root dir of my project, >>> ,i get page up and page down filled with missing dependencies from stuff >>> and "did you forget to inherit"-errors. (see error extract at the bottom) >>> >>> -I'm not sure if this has something to do with the "workdir", the >>> directory i stand in when i try to start the codeserver as described above, >>> some dependency declaration i'm missing or something else. >>> >>> -My dependencies should be ok since i can build it with the plugin, so >>> i'm a bit at a loss as to how make this work. >>> >>> -Help would be much appreciated, right now i can't develop and rolling >>> our project back to 2.8 and Java 8 wouldn't be great and take time. Man how >>> I wish that the intellij plugin had just kept working. >>> >>> as a final aside: >>> The "neither a gwt-lib or jar" warning messages in the error log below - >>> i still get it if i add the gwt-lib type to the dependency, and the >>> archetype project prints the same error when created. >>> >>> *Extract from the error log:* >>> >>> [INFO] Ignoring com.myproject:generalcommons:jar:1.0-SNAPSHOT; neither a >>> gwt-lib or jar:sources; Did you forget to use gwt-lib in the >>> dependency declaration? >>> [INFO] Ignoring com.myproject:webshared:jar:1.0-SNAPSHOT; neither a >>> gwt-lib or jar:sources; Did you forget to use gwt-lib in the >>> dependency declaration? >
Re: Really need help getting CodeServer to run with Java 11 and GWT 2.10
Hey Jens, thanks for replying! re. the gwt-type: 1. I only have one maven module that contains the entry point. the "gwt client" module 2. All dependencies are either on third-party such as Lombok, or my own other modules that only contain java classes and are built as jar-files. 3. I added the "type" gwt-lib to the dependencies in the "gwt client" pom, but I didn't do anything to the pom files in the jar modules that the gwt client depend on. I mean, Lombok doesn't have a packaging gwt-lib in its pom, either. On Friday 12 April 2024 at 11:15:38 UTC+2 Jens wrote: > A full example for multiple maven modules (more than just three) can be > found here: > https://github.com/tbroyer/gwt-maven-plugin/tree/main/src/it/e2e > > You have to add gwt-lib to your own maven library > modules that contain a module.gwt.xml file. Maybe you forgot that? > > -- J. > > Mathias schrieb am Freitag, 12. April 2024 um 07:50:42 UTC+2: > >> I *really* could use some help getting my project up for development >> after moving to gwt 2.10 and Java 11. >> I can unfortunately nolonger use the GWT intellij plugin i've loved and >> used for 12 years apparently, and i'm struggling a bit to get the >> codeserver running for my project. >> >> *CURRENT STATUS:* >> My project is over 12 years, but i migrated it from the old gwt mojo >> plugin to the new tbroyer one last year. >> It builds into a war fine and deploys on tomcat. Prior to the migration >> to GWT 2.10 (with new Jetty) and Java 11, i could run it with the GWT >> Intellij plugin, which I've loved and used for those same 12 years. >> But now the plugin unfortunately doesn't work, and from what I can tell >> due to the JettyLauncher, (I get lots of classnotfounds for for example >> javax.sql.DataSource) it's kind of impossible to make it run? So I thought >> I'd try what people have been saying, move to the manual thing with server >> and code server, even though it's a more cumbersome setup. >> >> As part of trying to get this show on the road, i created an archetype >> project and got codeserver and server running according to the new v2 >> tutorial. This works fine. >> >> *PROBLEM:* >> Basically i can't get the codeserver to run. My project is pretty large >> so my "webclient" module that contains my gwt client has a bunch of >> dependencies on my own child modules, and a couple of third-party ones such >> as Lombok. >> >> >> When i try the codeserver with this command (from the tutorial) >> * mvn gwt:codeserver -pl webclient -am* >> >> ,where the webclient is the module containing the gwt code and entry >> point, standing in the root dir of my project, >> ,i get page up and page down filled with missing dependencies from stuff >> and "did you forget to inherit"-errors. (see error extract at the bottom) >> >> -I'm not sure if this has something to do with the "workdir", the >> directory i stand in when i try to start the codeserver as described above, >> some dependency declaration i'm missing or something else. >> >> -My dependencies should be ok since i can build it with the plugin, so >> i'm a bit at a loss as to how make this work. >> >> -Help would be much appreciated, right now i can't develop and rolling >> our project back to 2.8 and Java 8 wouldn't be great and take time. Man how >> I wish that the intellij plugin had just kept working. >> >> as a final aside: >> The "neither a gwt-lib or jar" warning messages in the error log below - >> i still get it if i add the gwt-lib type to the dependency, and the >> archetype project prints the same error when created. >> >> *Extract from the error log:* >> >> [INFO] Ignoring com.myproject:generalcommons:jar:1.0-SNAPSHOT; neither a >> gwt-lib or jar:sources; Did you forget to use gwt-lib in the >> dependency declaration? >> [INFO] Ignoring com.myproject:webshared:jar:1.0-SNAPSHOT; neither a >> gwt-lib or jar:sources; Did you forget to use gwt-lib in the >> dependency declaration? >> [INFO] Ignoring com.myproject:webmaps:jar:1.0-SNAPSHOT; neither a gwt-lib >> or jar:sources; Did you forget to use gwt-lib in the >> dependency declaration? >> [INFO] Ignoring com.myproject:webshared:jar:1.0-SNAPSHOT; neither a >> gwt-lib or jar:sources; Did you forget to use gwt-lib in the >> dependency declaration? >> [INFO] Turning off precompile in incremental mode. >> [INFO] Super Dev Mode starting up >> [INFO]workDir: >> /Users/mathias/.projects/myproject/target/gwt/code
Re: Really need help getting CodeServer to run with Java 11 and GWT 2.10
Fair enough mate, I just remarked on it since when I built the archetype from scratch and saw that, my first thought was "huh wonder why that is, surely it won't work now since it doesn't pull in the classes from shared", but it did :) On Friday 12 April 2024 at 11:20:01 UTC+2 Thomas Broyer wrote: > On Friday, April 12, 2024 at 7:50:42 AM UTC+2 Mathias wrote: > > -My dependencies should be ok since i can build it with the plugin, so i'm > a bit at a loss as to how make this work. > > > Dependencies for gwt:compile and gwt:codeserver aren't the same: > https://tbroyer.github.io/gwt-maven-plugin/codeserver.html > You might have to either adjust the of dependencies (e.g. from > provided to compile) or adjust the gwt:codeserver's classpathScope (e.g. > from runtime to compile+runtime or compile) > > > as a final aside: > The "neither a gwt-lib or jar" warning messages in the error log below - i > still get it if i add the gwt-lib type to the dependency, and the archetype > project prints the same error when created. > > > Note that it's an info, not a warning > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/023512cf-2680-4f82-937e-ef853cb1e422n%40googlegroups.com.
Re: Really need help getting CodeServer to run with Java 11 and GWT 2.10
On Friday, April 12, 2024 at 7:50:42 AM UTC+2 Mathias wrote: -My dependencies should be ok since i can build it with the plugin, so i'm a bit at a loss as to how make this work. Dependencies for gwt:compile and gwt:codeserver aren't the same: https://tbroyer.github.io/gwt-maven-plugin/codeserver.html You might have to either adjust the of dependencies (e.g. from provided to compile) or adjust the gwt:codeserver's classpathScope (e.g. from runtime to compile+runtime or compile) as a final aside: The "neither a gwt-lib or jar" warning messages in the error log below - i still get it if i add the gwt-lib type to the dependency, and the archetype project prints the same error when created. Note that it's an info, not a warning -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/22b7fe06-6d3e-4215-979f-da5477c44508n%40googlegroups.com.
Re: Really need help getting CodeServer to run with Java 11 and GWT 2.10
A full example for multiple maven modules (more than just three) can be found here: https://github.com/tbroyer/gwt-maven-plugin/tree/main/src/it/e2e You have to add gwt-lib to your own maven library modules that contain a module.gwt.xml file. Maybe you forgot that? -- J. Mathias schrieb am Freitag, 12. April 2024 um 07:50:42 UTC+2: > I *really* could use some help getting my project up for development > after moving to gwt 2.10 and Java 11. > I can unfortunately nolonger use the GWT intellij plugin i've loved and > used for 12 years apparently, and i'm struggling a bit to get the > codeserver running for my project. > > *CURRENT STATUS:* > My project is over 12 years, but i migrated it from the old gwt mojo > plugin to the new tbroyer one last year. > It builds into a war fine and deploys on tomcat. Prior to the migration to > GWT 2.10 (with new Jetty) and Java 11, i could run it with the GWT Intellij > plugin, which I've loved and used for those same 12 years. > But now the plugin unfortunately doesn't work, and from what I can tell > due to the JettyLauncher, (I get lots of classnotfounds for for example > javax.sql.DataSource) it's kind of impossible to make it run? So I thought > I'd try what people have been saying, move to the manual thing with server > and code server, even though it's a more cumbersome setup. > > As part of trying to get this show on the road, i created an archetype > project and got codeserver and server running according to the new v2 > tutorial. This works fine. > > *PROBLEM:* > Basically i can't get the codeserver to run. My project is pretty large so > my "webclient" module that contains my gwt client has a bunch of > dependencies on my own child modules, and a couple of third-party ones such > as Lombok. > > > When i try the codeserver with this command (from the tutorial) > * mvn gwt:codeserver -pl webclient -am* > > ,where the webclient is the module containing the gwt code and entry > point, standing in the root dir of my project, > ,i get page up and page down filled with missing dependencies from stuff > and "did you forget to inherit"-errors. (see error extract at the bottom) > > -I'm not sure if this has something to do with the "workdir", the > directory i stand in when i try to start the codeserver as described above, > some dependency declaration i'm missing or something else. > > -My dependencies should be ok since i can build it with the plugin, so i'm > a bit at a loss as to how make this work. > > -Help would be much appreciated, right now i can't develop and rolling our > project back to 2.8 and Java 8 wouldn't be great and take time. Man how I > wish that the intellij plugin had just kept working. > > as a final aside: > The "neither a gwt-lib or jar" warning messages in the error log below - i > still get it if i add the gwt-lib type to the dependency, and the archetype > project prints the same error when created. > > *Extract from the error log:* > > [INFO] Ignoring com.myproject:generalcommons:jar:1.0-SNAPSHOT; neither a > gwt-lib or jar:sources; Did you forget to use gwt-lib in the > dependency declaration? > [INFO] Ignoring com.myproject:webshared:jar:1.0-SNAPSHOT; neither a > gwt-lib or jar:sources; Did you forget to use gwt-lib in the > dependency declaration? > [INFO] Ignoring com.myproject:webmaps:jar:1.0-SNAPSHOT; neither a gwt-lib > or jar:sources; Did you forget to use gwt-lib in the > dependency declaration? > [INFO] Ignoring com.myproject:webshared:jar:1.0-SNAPSHOT; neither a > gwt-lib or jar:sources; Did you forget to use gwt-lib in the > dependency declaration? > [INFO] Turning off precompile in incremental mode. > [INFO] Super Dev Mode starting up > [INFO]workDir: /Users/mathias/.projects/myproject/target/gwt/codeserver > [INFO][WARN] Deactivated PrecompressLinker > [INFO] 19:00:51.710 [main] INFO org.eclipse.jetty.util.log - Logging > initialized @778ms to org.eclipse.jetty.util.log.Slf4jLog > [INFO] 19:00:51.714 [main] DEBUG > org.eclipse.jetty.http.PreEncodedHttpField - HttpField encoders loaded: > [org.eclipse.jetty.http.Http1FieldPreEncoder] > [INFO]Loading Java files in com.myproject.client. > [INFO]Tracing compile failure path for type > 'com.myproject.client.domain.group.GroupDragDropLayout' > [INFO] [ERROR] Errors in > 'file:/Users/mathias/.projects/myproject/webgwtcommons/src/main/java/com/myproject/client/domain/group/GroupDragDropLayout.java' > [INFO] [ERROR] Line 18: The import lombok cannot be resolved > [INFO] [ERROR] Line 7: The import com.myproject.common cannot be > resolved > [INFO] [ERROR] Line 32: Getter cannot be resolved to a type &g
Really need help getting CodeServer to run with Java 11 and GWT 2.10
I *really* could use some help getting my project up for development after moving to gwt 2.10 and Java 11. I can unfortunately nolonger use the GWT intellij plugin i've loved and used for 12 years apparently, and i'm struggling a bit to get the codeserver running for my project. *CURRENT STATUS:* My project is over 12 years, but i migrated it from the old gwt mojo plugin to the new tbroyer one last year. It builds into a war fine and deploys on tomcat. Prior to the migration to GWT 2.10 (with new Jetty) and Java 11, i could run it with the GWT Intellij plugin, which I've loved and used for those same 12 years. But now the plugin unfortunately doesn't work, and from what I can tell due to the JettyLauncher, (I get lots of classnotfounds for for example javax.sql.DataSource) it's kind of impossible to make it run? So I thought I'd try what people have been saying, move to the manual thing with server and code server, even though it's a more cumbersome setup. As part of trying to get this show on the road, i created an archetype project and got codeserver and server running according to the new v2 tutorial. This works fine. *PROBLEM:* Basically i can't get the codeserver to run. My project is pretty large so my "webclient" module that contains my gwt client has a bunch of dependencies on my own child modules, and a couple of third-party ones such as Lombok. When i try the codeserver with this command (from the tutorial) * mvn gwt:codeserver -pl webclient -am* ,where the webclient is the module containing the gwt code and entry point, standing in the root dir of my project, ,i get page up and page down filled with missing dependencies from stuff and "did you forget to inherit"-errors. (see error extract at the bottom) -I'm not sure if this has something to do with the "workdir", the directory i stand in when i try to start the codeserver as described above, some dependency declaration i'm missing or something else. -My dependencies should be ok since i can build it with the plugin, so i'm a bit at a loss as to how make this work. -Help would be much appreciated, right now i can't develop and rolling our project back to 2.8 and Java 8 wouldn't be great and take time. Man how I wish that the intellij plugin had just kept working. as a final aside: The "neither a gwt-lib or jar" warning messages in the error log below - i still get it if i add the gwt-lib type to the dependency, and the archetype project prints the same error when created. *Extract from the error log:* [INFO] Ignoring com.myproject:generalcommons:jar:1.0-SNAPSHOT; neither a gwt-lib or jar:sources; Did you forget to use gwt-lib in the dependency declaration? [INFO] Ignoring com.myproject:webshared:jar:1.0-SNAPSHOT; neither a gwt-lib or jar:sources; Did you forget to use gwt-lib in the dependency declaration? [INFO] Ignoring com.myproject:webmaps:jar:1.0-SNAPSHOT; neither a gwt-lib or jar:sources; Did you forget to use gwt-lib in the dependency declaration? [INFO] Ignoring com.myproject:webshared:jar:1.0-SNAPSHOT; neither a gwt-lib or jar:sources; Did you forget to use gwt-lib in the dependency declaration? [INFO] Turning off precompile in incremental mode. [INFO] Super Dev Mode starting up [INFO]workDir: /Users/mathias/.projects/myproject/target/gwt/codeserver [INFO][WARN] Deactivated PrecompressLinker [INFO] 19:00:51.710 [main] INFO org.eclipse.jetty.util.log - Logging initialized @778ms to org.eclipse.jetty.util.log.Slf4jLog [INFO] 19:00:51.714 [main] DEBUG org.eclipse.jetty.http.PreEncodedHttpField - HttpField encoders loaded: [org.eclipse.jetty.http.Http1FieldPreEncoder] [INFO]Loading Java files in com.myproject.client. [INFO]Tracing compile failure path for type 'com.myproject.client.domain.group.GroupDragDropLayout' [INFO] [ERROR] Errors in 'file:/Users/mathias/.projects/myproject/webgwtcommons/src/main/java/com/myproject/client/domain/group/GroupDragDropLayout.java' [INFO] [ERROR] Line 18: The import lombok cannot be resolved [INFO] [ERROR] Line 7: The import com.myproject.common cannot be resolved [INFO] [ERROR] Line 32: Getter cannot be resolved to a type [INFO] [ERROR] Line 114: CSConstants cannot be resolved to a variable [INFO]Tracing compile failure path for type 'com.google.gwt.validation.client.impl.ConstraintFinderImpl' [INFO] [ERROR] Errors in 'jar:file:/Users/mathias/.m2/repository/org/gwtproject/gwt-user/2.10.0/gwt-user-2.10.0.jar!/com/google/gwt/validation/client/impl/ConstraintFinderImpl.java' [INFO] [ERROR] Line 38: No source code is available for type javax.validation.metadata.ElementDescriptor.ConstraintFinder; did you forget to inherit a required module? [INFO] [ERROR] Line 70: No source code is available for type javax.validation.metadata.ConstraintDescriptor; did you forget to inherit a required module? [INFO] [ERROR] Line
Re: Debugging the GWT application running in maven, version 2.11
The most up-to-date tutorial is https://www.gwtproject.org/gettingstarted-v2.html It uses maven to setup a best-practice GWT project which should consist of three modules. One module that contains your GWT code and basically represents your UI, one module that contains your server side code that will become a *.war file and will be deployed to a servlet container and finally a shared project which allows you to share some common code between the UI and your server. You don't have to use maven, but at least you can use the tutorial to get an idea on how a project layout should be. To debug your UI you have to use the browser dev tools and set breakpoints in the browser. To debug your server side code you would do it as with any other Java application and activate the Java Wire Debug Protocol (JWDP) on the JVM that runs the servlet container. -- J. Ayush Rawat schrieb am Donnerstag, 11. April 2024 um 09:08:26 UTC+2: > Recently I got a project on GWT. Had no idea what is this thing. Slowly > figured out things here and there. There aren't many sources to lean from. > I mostly went through ChatGPT and took help from it. It made me a demo > project for login page, sign up page and connecting it to the mysql > database. I worked on client-side, server-side and shared files. > > In this project I made login page, sign up page, user entity, user > service, user service async, user service implementation. As of now my > frontend is working fine but can't able to connect it to the database. I am > using Intellij Idea Ultimate version, and there is no way I can debug this > code. > > Will this community help me to figure this out by sharing resources and > you thoughts about this demo project. It's my third day working on this > task, and I can't see things moving. I really need your suggestions guys, > if needed can share my code in zip file. > > Also how can I debug this? > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/5ca25e42-280a-4840-871f-58cc1de7510dn%40googlegroups.com.
Debugging the GWT application running in maven, version 2.11
Recently I got a project on GWT. Had no idea what is this thing. Slowly figured out things here and there. There aren't many sources to lean from. I mostly went through ChatGPT and took help from it. It made me a demo project for login page, sign up page and connecting it to the mysql database. I worked on client-side, server-side and shared files. In this project I made login page, sign up page, user entity, user service, user service async, user service implementation. As of now my frontend is working fine but can't able to connect it to the database. I am using Intellij Idea Ultimate version, and there is no way I can debug this code. Will this community help me to figure this out by sharing resources and you thoughts about this demo project. It's my third day working on this task, and I can't see things moving. I really need your suggestions guys, if needed can share my code in zip file. Also how can I debug this? -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/7c5e8dd1-4a99-41a2-864e-75b31ba1d945n%40googlegroups.com.
Re: [ANN] JRS gwt-time 1.4.22/2.0.10 release
Hi, I'm using gwt-time (great work by the way), and I noticed that the TZDB is not updated for Mexico (two years ago Mexico stopped using DST). Is there a way to manually update the TZDB? Thanks in advance. On Sunday, October 30, 2022 at 10:29:50 AM UTC-6 foal wrote: > Hi, > > JRS gwt-time 1.4.22/2.0.10 has been released. > > >- TZDB 2022egtz >- CLDR 42 >- last updates from ThreeTen 1.6.3 release ( >https://github.com/ThreeTen/threetenbp) merged. > > > Details are on https://github.com/foal/gwt-time/releases/tag/v1.4.22 and > https://github.com/foal/gwt-time/releases/tag/v2.0.10 > > Project page - https://github.com/foal/gwt-time > > Best, > Stas > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/9f58ed8c-132c-4aae-9330-a692a43ff84fn%40googlegroups.com.
Re: [Resolved]- Unable to find 'com/google/common/collect/Collect.gwt.xml' : GWT 2.9
@Thomas : yes, that works too as it is stated in your documentation. Thanks. @Colin : Thanks for the hint. You're right, I added these 2 dependencies : com.google.j2objc j2objc-annotations false 3.0.0 com.google.errorprone error_prone_annotations 2.26.1 On Saturday, March 30, 2024 at 11:01:46 PM UTC+1 dja...@gmail.com wrote: > > You said : *" Also, the moduleTemplate configuration looks wrong, like > you've left an example placeholder in the configuration?", * > No, I don't think so, I moved the module.gwt.xml where the client/local > folder because the old project I want to migrate uses the old version of > mojo gwt-maven plugin and that's where the module is. Could that also be > part of my issue? I specified the path like that because the with Tbroyer > version, the gwt xml module file is not in the same place. > > > If you have a complete module file, you should rather skip the > `generate-module` goal by setting true rather than > defining (see > https://tbroyer.github.io/gwt-maven-plugin/migrating.html) > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/ffc0ba73-5e85-4a23-8a5e-3104256ae405n%40googlegroups.com.
Re: [ERROR] Unable to find 'com/google/common/collect/Collect.gwt.xml' : GWT 2.9
On Saturday, March 30, 2024 at 11:01:46 PM UTC+1 dja...@gmail.com wrote: You said : *" Also, the moduleTemplate configuration looks wrong, like you've left an example placeholder in the configuration?", * No, I don't think so, I moved the module.gwt.xml where the client/local folder because the old project I want to migrate uses the old version of mojo gwt-maven plugin and that's where the module is. Could that also be part of my issue? I specified the path like that because the with Tbroyer version, the gwt xml module file is not in the same place. If you have a complete module file, you should rather skip the `generate-module` goal by setting true rather than defining (see https://tbroyer.github.io/gwt-maven-plugin/migrating.html) -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/d8a82d2d-e8d4-4baa-bf23-9727e4c3e3d8n%40googlegroups.com.
Re: [ERROR] Unable to find 'com/google/common/collect/Collect.gwt.xml' : GWT 2.9
It appears that the error log you shared all boil down to missing j2objc
and errorprone annotations from your classpath.
My concern with your moduleTemplate was simply that you left the value as
"${project.basedir}/path/to/module/module.gwt.xml" - do you literally have
a directory called path/to/module/ in your project's base directory? I dont
think this is causing the problem though, nor is changing from one maven
plugin to another, but without a complete picture of your dependencies, it
is very hard to guess.
On Saturday, March 30, 2024 at 5:01:46 PM UTC-5 dja...@gmail.com wrote:
> Hi Colin,
>
> Thanks for your reply. Yes, that question is related. I just updated it on
> stack overflow. I added the the javax servlet dependency and that part was
> solved. And now I am facing another issue with the
> *com/google/common/collect/Collect.gwt.xml
> *module. Now you mentioned guava, I realized that I had it as a
> dependency, however I didn't added to my gwt module xml file. I just added
> it and I still have a bunch of errors in the guava-gwt classes now. I
> tried different version of guava as well (the latest one and the 23.0
> version).
>
> Tracing compile failure path for type
> 'com.google.common.collect.StandardTable'
> [INFO] [ERROR] Errors in
> 'jar:file:/C:/Users/MyUserName/.m2/repository/com/google/guava/guava-gwt/30.1-jre/guava-gwt-30.1-jre.jar!/com/google/common/collect/StandardTable.java'
> [INFO] [ERROR] Line 203: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 566: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 763: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 167: CanIgnoreReturnValue cannot be resolved
> to a type
> [INFO] [ERROR] Line 477: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 873: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 150: CanIgnoreReturnValue cannot be resolved
> to a type
> [INFO] [ERROR] Line 593: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 637: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 453: CanIgnoreReturnValue cannot be resolved
> to a type
> [INFO] [ERROR] Line 537: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 787: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 838: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 141: CanIgnoreReturnValue cannot be resolved
> to a type
> [INFO] [ERROR] Line 34: The import
> com.google.errorprone.annotations.CanIgnoreReturnValue cannot be resolved
> [INFO] [ERROR] Line 943: WeakOuter cannot be resolved to a type
> [INFO] [ERROR] Line 35: The import com.google.j2objc cannot be
> resolved
>
> [ERROR] Aborting compile due to errors in some input files
>
> You said : *" Also, the moduleTemplate configuration looks wrong, like
> you've left an example placeholder in the configuration?", *
> No, I don't think so, I moved the module.gwt.xml where the client/local
> folder because the old project I want to migrate uses the old version of
> mojo gwt-maven plugin and that's where the module is. Could that also be
> part of my issue? I specified the path like that because the with Tbroyer
> version, the gwt xml module file is not in the same place.
>
>
> Mnamo Jumamosi, 30 Machi 2024 saa 15:19:33 UTC-3 Colin Alworth aliandika:
>
>> This looks like the same question as
>> https://stackoverflow.com/questions/78202341/how-to-set-up-gwt-super-dev-mode-with-the-new-gwt-maven-plugin-with-a-web-applic,
>>
>> except with some updates - it sounds like you resolved the servlet
>> classpath issue, can you flesh out this example a little more to show what
>> else has happened, if that is also your question?
>>
>> It looks like guava-gwt is somehow not on your classpath, can you verify
>> this?
>>
>> Also, the moduleTemplate configuration looks wrong, like you've left an
>> example placeholder in the configuration?
>>
>> On Saturday, March 30, 2024 at 1:14:40 PM UTC-5 dja...@gmail.com wrote:
>>
>>> Hi,
>>> I am unable to build a multimodule demo project using GWT 2.9 using
>>> @Tbroyer gwt maven plugin. The reason I am still on this GWT version is
>>> because I am still using the Errai Framework that still depends on this
>>> particular version of GWT. I included the module that seems to be missing
>>> correctly and I still don't understand why it is missing.
>>>
>>> here is the error I am receiving when I run :
>>> *mvn clean install*
>>>
>>> *[I
Re: [ERROR] Unable to find 'com/google/common/collect/Collect.gwt.xml' : GWT 2.9
Hi Colin, Thanks for your reply. Yes, that question is related. I just updated it on stack overflow. I added the the javax servlet dependency and that part was solved. And now I am facing another issue with the *com/google/common/collect/Collect.gwt.xml *module. Now you mentioned guava, I realized that I had it as a dependency, however I didn't added to my gwt module xml file. I just added it and I still have a bunch of errors in the guava-gwt classes now. I tried different version of guava as well (the latest one and the 23.0 version). Tracing compile failure path for type 'com.google.common.collect.StandardTable' [INFO] [ERROR] Errors in 'jar:file:/C:/Users/MyUserName/.m2/repository/com/google/guava/guava-gwt/30.1-jre/guava-gwt-30.1-jre.jar!/com/google/common/collect/StandardTable.java' [INFO] [ERROR] Line 203: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 566: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 763: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 167: CanIgnoreReturnValue cannot be resolved to a type [INFO] [ERROR] Line 477: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 873: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 150: CanIgnoreReturnValue cannot be resolved to a type [INFO] [ERROR] Line 593: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 637: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 453: CanIgnoreReturnValue cannot be resolved to a type [INFO] [ERROR] Line 537: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 787: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 838: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 141: CanIgnoreReturnValue cannot be resolved to a type [INFO] [ERROR] Line 34: The import com.google.errorprone.annotations.CanIgnoreReturnValue cannot be resolved [INFO] [ERROR] Line 943: WeakOuter cannot be resolved to a type [INFO] [ERROR] Line 35: The import com.google.j2objc cannot be resolved [ERROR] Aborting compile due to errors in some input files You said : *" Also, the moduleTemplate configuration looks wrong, like you've left an example placeholder in the configuration?", * No, I don't think so, I moved the module.gwt.xml where the client/local folder because the old project I want to migrate uses the old version of mojo gwt-maven plugin and that's where the module is. Could that also be part of my issue? I specified the path like that because the with Tbroyer version, the gwt xml module file is not in the same place. Mnamo Jumamosi, 30 Machi 2024 saa 15:19:33 UTC-3 Colin Alworth aliandika: > This looks like the same question as > https://stackoverflow.com/questions/78202341/how-to-set-up-gwt-super-dev-mode-with-the-new-gwt-maven-plugin-with-a-web-applic, > > except with some updates - it sounds like you resolved the servlet > classpath issue, can you flesh out this example a little more to show what > else has happened, if that is also your question? > > It looks like guava-gwt is somehow not on your classpath, can you verify > this? > > Also, the moduleTemplate configuration looks wrong, like you've left an > example placeholder in the configuration? > > On Saturday, March 30, 2024 at 1:14:40 PM UTC-5 dja...@gmail.com wrote: > >> Hi, >> I am unable to build a multimodule demo project using GWT 2.9 using >> @Tbroyer gwt maven plugin. The reason I am still on this GWT version is >> because I am still using the Errai Framework that still depends on this >> particular version of GWT. I included the module that seems to be missing >> correctly and I still don't understand why it is missing. >> >> here is the error I am receiving when I run : >> *mvn clean install* >> >> *[INFO] --- gwt:1.1.0:compile (default-compile) @ sample-client ---* >> [INFO] Loading inherited module 'net.example.sample.App' >> [INFO]Loading inherited module 'org.jboss.errai.enterprise.All' >> [INFO] Loading inherited module 'org.jboss.errai.ioc.Container' >> [INFO] Loading inherited module >> 'com.google.common.collect.Collect' >> [INFO]* [ERROR] Unable to find >> 'com/google/common/collect/Collect.gwt.xml' on your classpath; could be a >> typo, or maybe you forgot to include a classpath entry for source?* >> [INFO] >> >> [INFO] Reactor Summary for Sample GWT UI 2.0-SNAPSHOT: >> [INFO] >> [INFO] Sample GWT UI .. FAILURE [ >> 7.079 s] >> [INFO] Sample-webapp .. SKIPPED >> [INFO]
Re: [ERROR] Unable to find 'com/google/common/collect/Collect.gwt.xml' : GWT 2.9
This looks like the same question as
https://stackoverflow.com/questions/78202341/how-to-set-up-gwt-super-dev-mode-with-the-new-gwt-maven-plugin-with-a-web-applic,
except with some updates - it sounds like you resolved the servlet
classpath issue, can you flesh out this example a little more to show what
else has happened, if that is also your question?
It looks like guava-gwt is somehow not on your classpath, can you verify
this?
Also, the moduleTemplate configuration looks wrong, like you've left an
example placeholder in the configuration?
On Saturday, March 30, 2024 at 1:14:40 PM UTC-5 dja...@gmail.com wrote:
> Hi,
> I am unable to build a multimodule demo project using GWT 2.9 using
> @Tbroyer gwt maven plugin. The reason I am still on this GWT version is
> because I am still using the Errai Framework that still depends on this
> particular version of GWT. I included the module that seems to be missing
> correctly and I still don't understand why it is missing.
>
> here is the error I am receiving when I run :
> *mvn clean install*
>
> *[INFO] --- gwt:1.1.0:compile (default-compile) @ sample-client ---*
> [INFO] Loading inherited module 'net.example.sample.App'
> [INFO]Loading inherited module 'org.jboss.errai.enterprise.All'
> [INFO] Loading inherited module 'org.jboss.errai.ioc.Container'
> [INFO] Loading inherited module
> 'com.google.common.collect.Collect'
> [INFO]* [ERROR] Unable to find
> 'com/google/common/collect/Collect.gwt.xml' on your classpath; could be a
> typo, or maybe you forgot to include a classpath entry for source?*
> [INFO]
> --------
> [INFO] Reactor Summary for Sample GWT UI 2.0-SNAPSHOT:
> [INFO]
> [INFO] Sample GWT UI .. FAILURE [
> 7.079 s]
> [INFO] Sample-webapp .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.356 s
> [INFO] Finished at: 2024-03-30T12:28:45-03:00
> [INFO]
>
>
> here is parts of my main pom.xml
>
>
>
>
>
> net.example.sample
> sample-client
> ${project.version}
> war
>
>
>
> com.google.gwt
> gwt
> ${gwt.version}
> pom
> import
>
>
>
>
>
>
>
> *org.jboss.errai.bom
> errai-bom
> ${errai.version}pom
> import *
>
>
>
> and parts of my module pom.xml
>
> sample-client
> gwt-app
>
> Sample GWT UI
>
>
>
> com.google.gwt
> gwt-dev
>
>
> org.eclipse.jetty
> apache-jsp
>
>
>
>
>
>
> com.google.gwt
> gwt-user
>
>
>
>
>
> * org.jboss.errai
> errai-javaee-all *
>
>
> org.jboss.errai
> errai-cdi-jboss
> runtime
>
>
>
>
>
> net.ltgt.gwt.maven
> gwt-maven-plugin
>
>
> ${project.basedir}/path/to/module/module.gwt.xml
> net.example.sample.App
> sample
>
>
>
>
>
> and this is the module inclusion in module.gwt.xml
>
> * *
>
> What am I missing?
> Please Advise.
>
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/f7a5aa4c-7666-4c52-aa80-9bd9ccbb1e63n%40googlegroups.com.
Re: Problem with GWT?
There really isn't enough information here to guess what is happen - what else could have changed, like server version or configuration, any errors in your browser dev tools console? On Tuesday, March 26, 2024 at 2:57:37 PM UTC-5 germ...@gmail.com wrote: > When I access the web page, it remains blank. I tried different browsers, > even on different computers, and they all showed the same problem. I am > using the gwt-2.8.2 SDK Until a few days ago, was it working correctly? > The curious thing is that the website works locally, that is, it is > normally displayed in the browser, but when the project is uploaded it is > not displayed. > Please I need help on what can happen. Thank you so much > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/93114622-43f1-478c-96a2-15208b8c91f6n%40googlegroups.com.
[ERROR] Unable to find 'com/google/common/collect/Collect.gwt.xml' : GWT 2.9
Hi,
I am unable to build a multimodule demo project using GWT 2.9 using
@Tbroyer gwt maven plugin. The reason I am still on this GWT version is
because I am still using the Errai Framework that still depends on this
particular version of GWT. I included the module that seems to be missing
correctly and I still don't understand why it is missing.
here is the error I am receiving when I run :
*mvn clean install*
*[INFO] --- gwt:1.1.0:compile (default-compile) @ sample-client ---*
[INFO] Loading inherited module 'net.example.sample.App'
[INFO]Loading inherited module 'org.jboss.errai.enterprise.All'
[INFO] Loading inherited module 'org.jboss.errai.ioc.Container'
[INFO] Loading inherited module 'com.google.common.collect.Collect'
[INFO]* [ERROR] Unable to find
'com/google/common/collect/Collect.gwt.xml' on your classpath; could be a
typo, or maybe you forgot to include a classpath entry for source?*
[INFO]
[INFO] Reactor Summary for Sample GWT UI 2.0-SNAPSHOT:
[INFO]
[INFO] Sample GWT UI .. FAILURE [
7.079 s]
[INFO] Sample-webapp .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 8.356 s
[INFO] Finished at: 2024-03-30T12:28:45-03:00
[INFO]
here is parts of my main pom.xml
net.example.sample
sample-client
${project.version}
war
com.google.gwt
gwt
${gwt.version}
pom
import
*org.jboss.errai.bom
errai-bom
${errai.version}pom
import *
and parts of my module pom.xml
sample-client
gwt-app
Sample GWT UI
com.google.gwt
gwt-dev
org.eclipse.jetty
apache-jsp
com.google.gwt
gwt-user
* org.jboss.errai
errai-javaee-all *
org.jboss.errai
errai-cdi-jboss
runtime
net.ltgt.gwt.maven
gwt-maven-plugin
${project.basedir}/path/to/module/module.gwt.xml
net.example.sample.App
sample
and this is the module inclusion in module.gwt.xml
* *
What am I missing?
Please Advise.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/13d8ea82-c155-471d-9373-8996baced686n%40googlegroups.com.
Re: i have applied below CSP policy and changed my GWT version to 2.8.2 after that i am getting below error for PRC call ( to read Database and populate the data in UI and save data to DB) and button
See https://github.com/gwtproject/gwt/issues/9578
On Wednesday, March 27, 2024 at 8:23:13 AM UTC+1 paparao@gmail.com
wrote:
> i have applied below CSP policy and changed my GWT version to 2.8.2
> after that i am getting below error for PRC call ( to read Database and
> populate the data in UI and save data to DB) and button click ( front
> validations , read data from DB ..etc).
>
> Error Details :
> java.lang.Exception: com.google.gwt.core.client.JavaScriptException:
> (EvalError) : Refused to evaluate a string as JavaScript because
> 'unsafe-eval' is not an allowed source of script in the following Content
> Security Policy directive: "script-src 'self' https://salesiq.zoho.com
> https://js.zohocdn.com https://static.zohocdn.com
> https://css.zohocdn.com/salesiq/ 'nonce-ByDmqt7tbtEnVEDxmZslig=='".
>
> my current csp policy :
> script-src 'self' https://salesiq.zoho.com https://js.zohocdn.com
> https://static.zohocdn.com https://css.zohocdn.com/salesiq/
> 'nonce-ByDmqt7tbtEnVEDxmZslig=='; object-src 'self'; img-src https: 'self'
> data:
>
> my current code to make RPC call :
>
> protected AsyncCallback>
> getTeamBillToCompaniesByUser()
>
> {
>
> final String methodName = "getTeamBillToCompaniesByUser: ";
>
> GWTLOG.info(methodName + " started");
>
> return new AsyncCallback>()
>
> {
>
> @Override
>
> public void onFailure(Throwable caught)
>
> {
>
> * Exception ex = new Exception(caught);*
>
> *GWTLOG.info(methodName + "onFailure" + "caught:" + ex);*
>
> }
>
> @Override
>
> public void onSuccess(List result)
>
> {
>
> GWTLOG.info(methodName + "onSuccess: billingAccnId: " + billingAccnId);
>
> updateBillToListBox(result, true); //boolean onload = true
>
> }
>
> };
>
> }
>
>
> based on browser console message error is with below code
>
>
> msg =
> com_google_gwt_logging_client_TextLogFormatter_$format__Lcom_google_gwt_logging_client_TextLogFormatter_2Ljava_util_logging_LogRecord_2Ljava_lang_String_2(this.java_util_logging_Handler_formatter,
>
> record);
> val = record.java_util_logging_LogRecord_level.intValue__I();
> val >= (java_util_logging_Level_$clinit__V(),
> $intern_38) ? (window.console.error(msg),
> undefined) : val >= 900 ? (window.console.warn(msg),
> undefined) : val >= 800 ? (window.console.info(msg),
> undefined) : (window.console.log(msg),
> undefined);
> $JsStackEmulator_stackDepth = JsStackEmulator_stackIndex - 1;
>
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/f03b64e4-b452-4b94-9e56-7863fc741203n%40googlegroups.com.
i have applied below CSP policy and changed my GWT version to 2.8.2 after that i am getting below error for PRC call ( to read Database and populate the data in UI and save data to DB) and button clic
i have applied below CSP policy and changed my GWT version to 2.8.2
after that i am getting below error for PRC call ( to read Database and
populate the data in UI and save data to DB) and button click ( front
validations , read data from DB ..etc).
Error Details :
java.lang.Exception: com.google.gwt.core.client.JavaScriptException:
(EvalError) : Refused to evaluate a string as JavaScript because
'unsafe-eval' is not an allowed source of script in the following Content
Security Policy directive: "script-src 'self' https://salesiq.zoho.com
https://js.zohocdn.com https://static.zohocdn.com
https://css.zohocdn.com/salesiq/ 'nonce-ByDmqt7tbtEnVEDxmZslig=='".
my current csp policy :
script-src 'self' https://salesiq.zoho.com https://js.zohocdn.com
https://static.zohocdn.com https://css.zohocdn.com/salesiq/
'nonce-ByDmqt7tbtEnVEDxmZslig=='; object-src 'self'; img-src https: 'self'
data:
my current code to make RPC call :
protected AsyncCallback> getTeamBillToCompaniesByUser()
{
final String methodName = "getTeamBillToCompaniesByUser: ";
GWTLOG.info(methodName + " started");
return new AsyncCallback>()
{
@Override
public void onFailure(Throwable caught)
{
* Exception ex = new Exception(caught);*
*GWTLOG.info(methodName + "onFailure" + "caught:" + ex);*
}
@Override
public void onSuccess(List result)
{
GWTLOG.info(methodName + "onSuccess: billingAccnId: " + billingAccnId);
updateBillToListBox(result, true); //boolean onload = true
}
};
}
based on browser console message error is with below code
msg =
com_google_gwt_logging_client_TextLogFormatter_$format__Lcom_google_gwt_logging_client_TextLogFormatter_2Ljava_util_logging_LogRecord_2Ljava_lang_String_2(this.java_util_logging_Handler_formatter,
record);
val = record.java_util_logging_LogRecord_level.intValue__I();
val >= (java_util_logging_Level_$clinit__V(),
$intern_38) ? (window.console.error(msg),
undefined) : val >= 900 ? (window.console.warn(msg),
undefined) : val >= 800 ? (window.console.info(msg),
undefined) : (window.console.log(msg),
undefined);
$JsStackEmulator_stackDepth = JsStackEmulator_stackIndex - 1;
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/759fc781-f361-4871-95f0-58e74267bf6an%40googlegroups.com.
GWT RPC call not working after apply CSP and change GWT version 2.8.2
i have applied below CSP policy and changed my GWT version to 2.8.2 after that i am getting below error for PRC call ( to read Database and populate the data in UI and save data to DB) and button click ( front validations , read data from DB ..etc). Error Details : java.lang.Exception: com.google.gwt.core.client.JavaScriptException: (EvalError) : Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' https://salesiq.zoho.com https://js.zohocdn.com https://static.zohocdn.com https://css.zohocdn.com/salesiq/ 'nonce-ByDmqt7tbtEnVEDxmZslig=='". my current csp policy : script-src 'self' https://salesiq.zoho.com https://js.zohocdn.com https://static.zohocdn.com https://css.zohocdn.com/salesiq/ 'nonce-ByDmqt7tbtEnVEDxmZslig=='; object-src 'self'; img-src https: 'self' data: -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a73c25ec-d022-4927-8019-f6c428c2f6ddn%40googlegroups.com.
Problem with GWT?
When I access the web page, it remains blank. I tried different browsers, even on different computers, and they all showed the same problem. I am using the gwt-2.8.2 SDK Until a few days ago, was it working correctly? The curious thing is that the website works locally, that is, it is normally displayed in the browser, but when the project is uploaded it is not displayed. Please I need help on what can happen. Thank you so much -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/643cb5ec-7d07-4bae-baa3-535d931b2ed2n%40googlegroups.com.
Re: Issue with tomcat version of GWT 2.11 for class javax.validation.Path
For whatever it might be worth... I just went through a possibly similar exercise, getting my 2.11 GWT-RPC-based app to run with Tomcat 10. I had to run around my codebase and replace 'javax' with 'jakarta', but the last key step was ensuring that my GWTRPC services inherited from this class: com.google.gwt.user.server.rpc.*jakarta*.RemoteServiceServlet Note the .jakarta. in there, which otherwise is not present (in javax form) in the older/other class hierarchy -- a different package entirely. Also note, my project is not using 'validation-api.jar' directly (not sure about indirectly), so I can't promise the above will help -- sorry. On Wednesday, March 20, 2024 at 5:45:24 AM UTC-4 Priya wrote: > Hi Team, > > We are working on development environment with Tomcat 10 where third party > jar *jakarta.validation-api.jar *has been updated to tomcat specific > version where package structure is changed from javax.validation to > jakarta.validation. > > When GWT 2.11 with tomcat specific jars(Gwt-servlet and > requestfactory-server.jar) are deployed, it is trying to find > javax.validation.Path with below stack trace- > > Exception while dispatching incoming RPC call > java.lang.NoClassDefFoundError: javax/validation/Path > java.base/java.lang.Class.forName(Class.java:467) > at > com.google.gwt.user.server.rpc.SerializationPolicyLoader.loadFromStream(SerializationPolicyLoader.java:217) > at > com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet.loadSerializationPolicy(RemoteServiceServlet.java:98) > at > com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet.doGetSerializationPolicy(RemoteServiceServlet.java:437) > at > com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet.getSerializationPolicy(RemoteServiceServlet.java:251) > at > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead(ServerSerializationStreamReader.java:505) > at com.google.gwt.user.server.rpc.jakarta.RPC.decodeRequest(RPC.java:241) > > As this package has been changed in our environment to > jakarta.validation.path, GWT source code is unable to find this class, > giving NoClassDefFoundError. > > Also we can find several references of javax.validation.Path in gwt-user > and other jars under GWT 2.11 jars. > > My queries are - > 1. Has anyone come across such error, if yes, what is workaround. > 2. as javax packages are outdated and replaced by jakarta, is there a plan > to update them and what is significance of those classes .Also, how this > failure can be addressed. > 3. One solution I could see for older releases, is to add dependency for > gwt-servlet-deps.jar, but that is not viable solution to us,as we are > moving away from javax packages due to tomcat upgrade. > > Any immediate help will be appreciated. > Thanks! > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f9db97be-397f-4bfe-a13a-de001fdcd311n%40googlegroups.com.
Issue with tomcat version of GWT 2.11 for class javax.validation.Path
Hi Team, We are working on development environment with Tomcat 10 where third party jar *jakarta.validation-api.jar *has been updated to tomcat specific version where package structure is changed from javax.validation to jakarta.validation. When GWT 2.11 with tomcat specific jars(Gwt-servlet and requestfactory-server.jar) are deployed, it is trying to find javax.validation.Path with below stack trace- Exception while dispatching incoming RPC call java.lang.NoClassDefFoundError: javax/validation/Path java.base/java.lang.Class.forName(Class.java:467) at com.google.gwt.user.server.rpc.SerializationPolicyLoader.loadFromStream(SerializationPolicyLoader.java:217) at com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet.loadSerializationPolicy(RemoteServiceServlet.java:98) at com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet.doGetSerializationPolicy(RemoteServiceServlet.java:437) at com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet.getSerializationPolicy(RemoteServiceServlet.java:251) at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead(ServerSerializationStreamReader.java:505) at com.google.gwt.user.server.rpc.jakarta.RPC.decodeRequest(RPC.java:241) As this package has been changed in our environment to jakarta.validation.path, GWT source code is unable to find this class, giving NoClassDefFoundError. Also we can find several references of javax.validation.Path in gwt-user and other jars under GWT 2.11 jars. My queries are - 1. Has anyone come across such error, if yes, what is workaround. 2. as javax packages are outdated and replaced by jakarta, is there a plan to update them and what is significance of those classes .Also, how this failure can be addressed. 3. One solution I could see for older releases, is to add dependency for gwt-servlet-deps.jar, but that is not viable solution to us,as we are moving away from javax packages due to tomcat upgrade. Any immediate help will be appreciated. Thanks! -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CANu4zMwruOi-sXgWftXUcCUZzPGT1-8Ao-n%3DHk7M5w2aEO4NGw%40mail.gmail.com.
Re: gwt-maven-springboot-archetype updated ...
Thank you Frank for making the excellent tool! Just checked the changes, working perfectly. On Monday 4 March 2024 at 7:55:58 pm UTC+11 Frank Hossfeld wrote: > Thanks Craig for contributing. New version is online. > > Frank Hossfeld schrieb am Dienstag, 6. Februar 2024 um 08:11:15 UTC+1: > >> new version is online ... >> >> Craig Mitchell schrieb am Montag, 5. Februar 2024 um 02:13:45 UTC+1: >> >>> Done: >>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/4 >>> Cheers. >>> >>> On Monday 5 February 2024 at 3:59:55 am UTC+11 Frank Hossfeld wrote: >>> >>>> Please can you open an issue regarding the gwt-servlet-jakarta problem >>>> ... >>>> >>>> Thanks >>>> >>>> Craig Mitchell schrieb am Sonntag, 4. Februar 2024 um 04:57:34 UTC+1: >>>> >>>>> I noticed that it always logs the error: >>>>> >>>>> ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not >>>>> found; did you forget to include it in this deployment? >>>>> >>>>> on the first RPC call. The RPC still seems to work fine, but >>>>> wondering if this is an issue or not? >>>>> >>>>> Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"? >>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16 >>>>> >>>>> >>>>> Thanks. >>>>> >>>>> On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell wrote: >>>>> >>>>>> Just realised you can also set it in your server pom.xml, in the >>>>>> Spring Boot Maven plugin (configuration > jvmArguments), instead of the >>>>>> launcher: >>>>>> >>>>>> >>>>>> org.springframework.boot >>>>>> spring-boot-maven-plugin >>>>>> >>>>>> >>>>>> >>>>>> repackage >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> false >>>>>> >>>>>> >>>>>> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote: >>>>>> >>>>>>> Thanks Thomas. Now switched to: >>>>>>> >>>>>>> >>>>>>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>>>>> >>>>>>> [image: Screen.png] >>>>>>> >>>>>>> Which also works great. >>>>>>> >>>>>>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote: >>>>>>> >>>>>>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) >>>>>>>> rather than the legacy -Xdebug -Xrunjdwp (and then you no longer need >>>>>>>> the >>>>>>>> quotes ) >>>>>>>> >>>>>>>> And when I say legacy, I really mean it: already in Java 8 -Xdebug >>>>>>>> does nothing ( >>>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) >>>>>>>> >>>>>>>> and Xrunjdwp is superceded by agentlib ( >>>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG >>>>>>>> ) >>>>>>>> >>>>>>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 >>>>>>>> ma...@craig-mitchell.com wrote: >>>>>>>> >>>>>>>>> Thank you! Working great now (quotes were important). >>>>>>>>> >>>>>>>>> [image: Screen.png] >>>>>>>>> >>>>>>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Mmmh, it might be worth adding this information to the archetype >>>>>>>>>> docs. >>>>>>>>>> >>>>>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/bec9bbcc-741f-4e49-be12-8dd572abd2ecn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Thanks Craig for contributing. New version is online. Frank Hossfeld schrieb am Dienstag, 6. Februar 2024 um 08:11:15 UTC+1: > new version is online ... > > Craig Mitchell schrieb am Montag, 5. Februar 2024 um 02:13:45 UTC+1: > >> Done: https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/4 >> Cheers. >> >> On Monday 5 February 2024 at 3:59:55 am UTC+11 Frank Hossfeld wrote: >> >>> Please can you open an issue regarding the gwt-servlet-jakarta problem >>> ... >>> >>> Thanks >>> >>> Craig Mitchell schrieb am Sonntag, 4. Februar 2024 um 04:57:34 UTC+1: >>> >>>> I noticed that it always logs the error: >>>> >>>> ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not >>>> found; did you forget to include it in this deployment? >>>> >>>> on the first RPC call. The RPC still seems to work fine, but wondering >>>> if this is an issue or not? >>>> >>>> Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"? >>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16 >>>> >>>> >>>> Thanks. >>>> >>>> On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell wrote: >>>> >>>>> Just realised you can also set it in your server pom.xml, in the >>>>> Spring Boot Maven plugin (configuration > jvmArguments), instead of the >>>>> launcher: >>>>> >>>>> >>>>> org.springframework.boot >>>>> spring-boot-maven-plugin >>>>> >>>>> >>>>> >>>>> repackage >>>>> >>>>> >>>>> >>>>> >>>>> false >>>>> >>>>> >>>>> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>>> >>>>> >>>>> >>>>> >>>>> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote: >>>>> >>>>>> Thanks Thomas. Now switched to: >>>>>> >>>>>> >>>>>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>>>> >>>>>> [image: Screen.png] >>>>>> >>>>>> Which also works great. >>>>>> >>>>>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote: >>>>>> >>>>>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) >>>>>>> rather than the legacy -Xdebug -Xrunjdwp (and then you no longer need >>>>>>> the >>>>>>> quotes ) >>>>>>> >>>>>>> And when I say legacy, I really mean it: already in Java 8 -Xdebug >>>>>>> does nothing ( >>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) >>>>>>> >>>>>>> and Xrunjdwp is superceded by agentlib ( >>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG >>>>>>> ) >>>>>>> >>>>>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 >>>>>>> ma...@craig-mitchell.com wrote: >>>>>>> >>>>>>>> Thank you! Working great now (quotes were important). >>>>>>>> >>>>>>>> [image: Screen.png] >>>>>>>> >>>>>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Mmmh, it might be worth adding this information to the archetype >>>>>>>>> docs. >>>>>>>>> >>>>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/eb6c1cdc-d862-496a-b9d3-e7a0fd026552n%40googlegroups.com.
I can't change the language in my cloud-deployed GWT application
I can't change the language in my cloud-deployed GWT application. Locally, using eclipse, everything works fine. But the same application deployed in the cloud it shows me the "default" label as the default language, while everything on the page is in English Then when I try to switch to the Italian language from the combo box, the page is reloaded but the "default" label still remains in the combo and the page also remains in English. Any ideas/suggestions for fixing? Thanks in advance -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/fa86f1c9-ba45-46de-86cb-7dca6da8058fn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
new version is online ... Craig Mitchell schrieb am Montag, 5. Februar 2024 um 02:13:45 UTC+1: > Done: https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/4 > Cheers. > > On Monday 5 February 2024 at 3:59:55 am UTC+11 Frank Hossfeld wrote: > >> Please can you open an issue regarding the gwt-servlet-jakarta problem ... >> >> Thanks >> >> Craig Mitchell schrieb am Sonntag, 4. Februar 2024 um 04:57:34 UTC+1: >> >>> I noticed that it always logs the error: >>> >>> ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not >>> found; did you forget to include it in this deployment? >>> >>> on the first RPC call. The RPC still seems to work fine, but wondering >>> if this is an issue or not? >>> >>> Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"? >>> https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16 >>> >>> >>> Thanks. >>> >>> On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell wrote: >>> >>>> Just realised you can also set it in your server pom.xml, in the Spring >>>> Boot Maven plugin (configuration > jvmArguments), instead of the launcher: >>>> >>>> >>>> org.springframework.boot >>>> spring-boot-maven-plugin >>>> >>>> >>>> >>>> repackage >>>> >>>> >>>> >>>> >>>> false >>>> >>>> >>>> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>> >>>> >>>> >>>> >>>> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote: >>>> >>>>> Thanks Thomas. Now switched to: >>>>> >>>>> >>>>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>>> >>>>> [image: Screen.png] >>>>> >>>>> Which also works great. >>>>> >>>>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote: >>>>> >>>>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather >>>>>> than the legacy -Xdebug -Xrunjdwp (and then you no longer need the >>>>>> quotes ) >>>>>> >>>>>> And when I say legacy, I really mean it: already in Java 8 -Xdebug >>>>>> does nothing ( >>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) >>>>>> >>>>>> and Xrunjdwp is superceded by agentlib ( >>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG >>>>>> ) >>>>>> >>>>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 >>>>>> ma...@craig-mitchell.com wrote: >>>>>> >>>>>>> Thank you! Working great now (quotes were important). >>>>>>> >>>>>>> [image: Screen.png] >>>>>>> >>>>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld >>>>>>> wrote: >>>>>>> >>>>>>>> Mmmh, it might be worth adding this information to the archetype >>>>>>>> docs. >>>>>>>> >>>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f8264e2d-f557-47b2-bfbc-12a45067a24an%40googlegroups.com.
Re: Had a problem trying GWT 2.11.0
Just published version 2024.2.5 of the archetypes that adds a DOCTYPE linking to the DTD to the context.xml. I could reproduce the jetty_overlays error in env=prod, but that really looks like a bug in the jetty-maven-plugin (and creating the directory allows the server to start, but it was still missing the overlay, so no *.nocache.js loaded from the HTML host page). On Sunday, February 4, 2024 at 6:43:59 PM UTC+1 jamal@gmail.com wrote: > After generating a project skeleton using the latest gwt-maven-archetypes > <https://github.com/tbroyer/gwt-maven-archetypes>, done the usual: > - mvn gwt:codeserver -pl *-client -am > - mvn jetty:run -pl *-server -am -Denv=dev > > The first command executed without problems, however the second one failed > to start jetty showing on terminal the following error: > > [*ERROR*] *SAX Parse Issue @null line:1 col:59 : > org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 59; > cvc-elt.1.a: Cannot find the declaration of element 'Configure'.* > [*INFO*] > *----* > [*INFO*] > *Reactor Summary for gwt-gpt 1.0-SNAPSHOT:*[*INFO*] > [*INFO*] gwt-gpt ........ *SUCCESS* > [ 5.841 s] > [*INFO*] gwt-gpt-shared ..... *SUCCESS* > [ 1.400 s] > [*INFO*] gwt-gpt-server . *FAILURE* > [ 0.703 s] > [*INFO*] > ** > [*INFO*] > *BUILD FAILURE*[*INFO*] > ** > [*INFO*] Total time: 14.168 s > [*INFO*] Finished at: 2024-02-04T16:51:35Z > [*INFO*] > ** > After many searches I found that *context.xml* in *jettyconf* folder had > missing dtd schema. Adding that as follows jetty started with no error: > > * "http://www.eclipse.org/jetty/configure.dtd > <http://www.eclipse.org/jetty/configure.dtd>">* > > > org.eclipse.jetty.servlet.Default.useFileMappedBuffer > false > > > > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/359d90ba-dbdf-45d4-9bc0-b687d99cf724n%40googlegroups.com.
Re: Had a problem trying GWT 2.11.0
I also found that out eventually. Another thing: The server module needs /target /jetty_overlays folder for running env-prod. On Sunday, February 4, 2024 at 5:43:59 PM UTC jamal@gmail.com wrote: > After generating a project skeleton using the latest gwt-maven-archetypes > <https://github.com/tbroyer/gwt-maven-archetypes>, done the usual: > - mvn gwt:codeserver -pl *-client -am > - mvn jetty:run -pl *-server -am -Denv=dev > > The first command executed without problems, however the second one failed > to start jetty showing on terminal the following error: > > [*ERROR*] *SAX Parse Issue @null line:1 col:59 : > org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 59; > cvc-elt.1.a: Cannot find the declaration of element 'Configure'.* > [*INFO*] > *----* > [*INFO*] > *Reactor Summary for gwt-gpt 1.0-SNAPSHOT:*[*INFO*] > [*INFO*] gwt-gpt ........ *SUCCESS* > [ 5.841 s] > [*INFO*] gwt-gpt-shared ..... *SUCCESS* > [ 1.400 s] > [*INFO*] gwt-gpt-server . *FAILURE* > [ 0.703 s] > [*INFO*] > ** > [*INFO*] > *BUILD FAILURE*[*INFO*] > ** > [*INFO*] Total time: 14.168 s > [*INFO*] Finished at: 2024-02-04T16:51:35Z > [*INFO*] > ** > After many searches I found that *context.xml* in *jettyconf* folder had > missing dtd schema. Adding that as follows jetty started with no error: > > * "http://www.eclipse.org/jetty/configure.dtd > <http://www.eclipse.org/jetty/configure.dtd>">* > > > org.eclipse.jetty.servlet.Default.useFileMappedBuffer > false > > > > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4b4f11f4-98c7-46cd-95ef-dcaf7c975f5en%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Done: https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/4 Cheers. On Monday 5 February 2024 at 3:59:55 am UTC+11 Frank Hossfeld wrote: > Please can you open an issue regarding the gwt-servlet-jakarta problem ... > > Thanks > > Craig Mitchell schrieb am Sonntag, 4. Februar 2024 um 04:57:34 UTC+1: > >> I noticed that it always logs the error: >> >> ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not >> found; did you forget to include it in this deployment? >> >> on the first RPC call. The RPC still seems to work fine, but wondering >> if this is an issue or not? >> >> Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"? >> https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16 >> >> >> Thanks. >> >> On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell wrote: >> >>> Just realised you can also set it in your server pom.xml, in the Spring >>> Boot Maven plugin (configuration > jvmArguments), instead of the launcher: >>> >>> >>> org.springframework.boot >>> spring-boot-maven-plugin >>> >>> >>> >>> repackage >>> >>> >>> >>> >>> false >>> >>> >>> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>> >>> >>> >>> >>> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote: >>> >>>> Thanks Thomas. Now switched to: >>>> >>>> >>>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>>> >>>> [image: Screen.png] >>>> >>>> Which also works great. >>>> >>>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote: >>>> >>>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather >>>>> than the legacy -Xdebug -Xrunjdwp (and then you no longer need the >>>>> quotes ) >>>>> >>>>> And when I say legacy, I really mean it: already in Java 8 -Xdebug >>>>> does nothing ( >>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) >>>>> >>>>> and Xrunjdwp is superceded by agentlib ( >>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG >>>>> ) >>>>> >>>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 >>>>> ma...@craig-mitchell.com wrote: >>>>> >>>>>> Thank you! Working great now (quotes were important). >>>>>> >>>>>> [image: Screen.png] >>>>>> >>>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote: >>>>>> >>>>>>> Mmmh, it might be worth adding this information to the archetype >>>>>>> docs. >>>>>>> >>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/240ba6fb-e55e-4130-850e-c558f7ae5f93n%40googlegroups.com.
Had a problem trying GWT 2.11.0
After generating a project skeleton using the latest gwt-maven-archetypes <https://github.com/tbroyer/gwt-maven-archetypes>, done the usual: - mvn gwt:codeserver -pl *-client -am - mvn jetty:run -pl *-server -am -Denv=dev The first command executed without problems, however the second one failed to start jetty showing on terminal the following error: [*ERROR*] *SAX Parse Issue @null line:1 col:59 : org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 59; cvc-elt.1.a: Cannot find the declaration of element 'Configure'.* [*INFO*] **[ *INFO*] *Reactor Summary for gwt-gpt 1.0-SNAPSHOT:*[*INFO*] [*INFO*] gwt-gpt *SUCCESS* [ 5.841 s] [*INFO*] gwt-gpt-shared . *SUCCESS* [ 1.400 s] [*INFO*] gwt-gpt-server . *FAILURE* [ 0.703 s] [*INFO*] **[ *INFO*] *BUILD FAILURE*[*INFO*] **[ *INFO*] Total time: 14.168 s [*INFO*] Finished at: 2024-02-04T16:51:35Z [*INFO*] ** After many searches I found that *context.xml* in *jettyconf* folder had missing dtd schema. Adding that as follows jetty started with no error: *http://www.eclipse.org/jetty/configure.dtd;>* org.eclipse.jetty.servlet.Default.useFileMappedBuffer false -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1685f6cc-c16f-4b8b-9b41-97bc81bf1139n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Please can you open an issue regarding the gwt-servlet-jakarta problem ... Thanks Craig Mitchell schrieb am Sonntag, 4. Februar 2024 um 04:57:34 UTC+1: > I noticed that it always logs the error: > > ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not > found; did you forget to include it in this deployment? > > on the first RPC call. The RPC still seems to work fine, but wondering if > this is an issue or not? > > Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"? > https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16 > > > Thanks. > > On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell wrote: > >> Just realised you can also set it in your server pom.xml, in the Spring >> Boot Maven plugin (configuration > jvmArguments), instead of the launcher: >> >> >> org.springframework.boot >> spring-boot-maven-plugin >> >> >> >> repackage >> >> >> >> >> false >> >> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >> >> >> >> >> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote: >> >>> Thanks Thomas. Now switched to: >>> >>> >>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >>> >>> [image: Screen.png] >>> >>> Which also works great. >>> >>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote: >>> >>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather >>>> than the legacy -Xdebug -Xrunjdwp (and then you no longer need the >>>> quotes ) >>>> >>>> And when I say legacy, I really mean it: already in Java 8 -Xdebug does >>>> nothing ( >>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) >>>> >>>> and Xrunjdwp is superceded by agentlib ( >>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG >>>> ) >>>> >>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 >>>> ma...@craig-mitchell.com wrote: >>>> >>>>> Thank you! Working great now (quotes were important). >>>>> >>>>> [image: Screen.png] >>>>> >>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote: >>>>> >>>>>> Mmmh, it might be worth adding this information to the archetype docs. >>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/01839f4b-fe49-4533-bd82-43608e3dc323n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
I noticed that it always logs the error: ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not found; did you forget to include it in this deployment? on the first RPC call. The RPC still seems to work fine, but wondering if this is an issue or not? Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"? https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16 Thanks. On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell wrote: > Just realised you can also set it in your server pom.xml, in the Spring > Boot Maven plugin (configuration > jvmArguments), instead of the launcher: > > > org.springframework.boot > spring-boot-maven-plugin > > > > repackage > > > > > false > > -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 > > > > > On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote: > >> Thanks Thomas. Now switched to: >> >> >> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 >> >> [image: Screen.png] >> >> Which also works great. >> >> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote: >> >>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather >>> than the legacy -Xdebug -Xrunjdwp (and then you no longer need the >>> quotes ) >>> >>> And when I say legacy, I really mean it: already in Java 8 -Xdebug does >>> nothing ( >>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) >>> >>> and Xrunjdwp is superceded by agentlib ( >>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG >>> ) >>> >>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 >>> ma...@craig-mitchell.com wrote: >>> >>>> Thank you! Working great now (quotes were important). >>>> >>>> [image: Screen.png] >>>> >>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote: >>>> >>>>> Mmmh, it might be worth adding this information to the archetype docs. >>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/3e0a9e6d-3481-4565-948f-21fb3f6a75b4n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Just realised you can also set it in your server pom.xml, in the Spring Boot Maven plugin (configuration > jvmArguments), instead of the launcher: org.springframework.boot spring-boot-maven-plugin repackage false -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote: > Thanks Thomas. Now switched to: > > > -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 > > [image: Screen.png] > > Which also works great. > > On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote: > >> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather >> than the legacy -Xdebug -Xrunjdwp (and then you no longer need the >> quotes ) >> >> And when I say legacy, I really mean it: already in Java 8 -Xdebug does >> nothing ( >> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) >> >> and Xrunjdwp is superceded by agentlib ( >> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG >> ) >> >> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 >> ma...@craig-mitchell.com wrote: >> >>> Thank you! Working great now (quotes were important). >>> >>> [image: Screen.png] >>> >>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote: >>> >>>> Mmmh, it might be worth adding this information to the archetype docs. >>>> >>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/103b2e21-3427-476d-bda8-d6c38766d7f7n%40googlegroups.com.
Re: Question about setting GWT RPC timeout
You could just create a generic method to do is for all your
GWT.create(service) services. Eg:
public static void setTimeout(ServerAsync myService) {
myService.setRpcRequestBuilder(new RpcRequestBuilder() {
@Override
protected RequestBuilder doCreate(String serviceEntryPoint) {
RequestBuilder builder = new RequestBuilder(RequestBuilder.POST,
serviceEntryPoint);
builder.setTimeoutMillis(3); // 30 second timeout
return builder;
}
});
return myService;
}
ServerAsync myService1 = setTimeout(GWT.create(service1));
ServerAsync myService2 = setTimeout(GWT.create(service2));
On Friday 2 February 2024 at 10:06:24 am UTC+11 Blaze wrote:
> Hi all,
>
> I came across this thread, I have searched if there is some "global"
> request timeout that we can set on a RPC calls, not RequestBuilder, but the
> one from RemoteService created via GWT.create(service) ?
> I coudnt find anything, any idea?
>
> Tnx
>
> On Thursday, April 6, 2023 at 2:16:47 PM UTC+2 Colin Alworth wrote:
>
>> What you're looking for is a way to re-try requests in the case where the
>> server is unreachable, which is not something that HTTP or the browser
>> gives you automatically. If you had a proxy, but the server itself was
>> down, the proxy would likely return a 503 service unavailable status, which
>> the client could use to retry until the service was available (which might
>> only happen for a certain number of seconds or a certain number of tries).
>> It might also be possible for a proxy to wait and retry the upstream server
>> until it was available, but I can't think of a proxy right now with that
>> feature.
>>
>> HTTP itself doesn't have a timeout feature at all either. The timeout
>> that you're setting on the client side is a simple GWT Timer, if the
>> request hasn't finished (either in success or failure), it cancels the
>> upstream request and presents the failure you're seeing to the client.
>>
>> Be a little careful when implementing a retry mechanism, as it is
>> possible that the call made it to the server, and the server performed the
>> action, but the client lost internet connection while the response was on
>> its way to the client - that is, retrying a non-idempotent or expensive
>> action may cause problems you weren't expecting. A status code of 0 is
>> usually the client's way of saying "I wasn't able to get any reply from the
>> server for some reason" - taking that information and trying to do
>> something simple and idempotent until a server connection can be
>> reestablished lets you know that the server and network are both working
>> again, followed by some "did my last action succeed" before trying again
>> (or just let the user dismiss the message and try again) will help mitigate
>> this class of issues. A proxy sending back a 503 is a safer way to be sure
>> that the network connection is good, but only the server is down, so you
>> can retry - but be aware that technically there might be a network issue
>> between the proxy and server, though this is much less likely.
>>
>> Good luck,
>> Colin
>>
>> On Thursday, April 6, 2023 at 7:05:53 AM UTC-5 Dmitri wrote:
>>
>>> Dear Colin
>>>
>>> Thank you so much for your advice. I'll take a closer look at those
>>> areas.
>>>
>>> Just a little clarification: The server is not running at all. Both
>>> exceptions are generated from the client only with different timeout
>>> settings when it cannot reach the server.
>>> When the server is running - no problems in both cases. The purpose of
>>> the code is to make the client wait longer when the server is unreachable
>>> due to temporary communication problems.
>>>
>>> PS there are some typos in the codes I provide which I made when
>>> clean-up for posting., Please ignore them.
>>> Thank you again
>>>
>>> Best regards
>>> Dmitri
>>>
>>>
>>> On Thu, Apr 6, 2023 at 9:49 PM Colin Alworth wrote:
>>>
>>>> I believe you're experiencing different timeouts in different cases.
>>>> That is, the problem you're facing of a short timeout before you use your
>>>> RPC_TIMEOUT_MS is a server-side timeout (or potentially a proxy?), but
>>>> after you set a client-side timeout, the client is observing that the
>>>> server is taking too long, and terminating the call from its side,
>>>> resulting in the RequestTimeoutException.
>>>>
>>>> To confirm this, try setting the client-side timeo
Re: Question about setting GWT RPC timeout
You can set the request builder on the GWT.create(service). Ie:
ServerAsync myService = GWT.create(service);
myService.setRpcRequestBuilder(new RpcRequestBuilder() {
@Override
protected RequestBuilder doCreate(String serviceEntryPoint) {
RequestBuilder builder = new RequestBuilder(RequestBuilder.POST,
serviceEntryPoint);
builder.setTimeoutMillis(3); // 30 second timeout
return builder;
}
});
On Friday 2 February 2024 at 10:06:24 am UTC+11 Blaze wrote:
> Hi all,
>
> I came across this thread, I have searched if there is some "global"
> request timeout that we can set on a RPC calls, not RequestBuilder, but the
> one from RemoteService created via GWT.create(service) ?
> I coudnt find anything, any idea?
>
> Tnx
>
> On Thursday, April 6, 2023 at 2:16:47 PM UTC+2 Colin Alworth wrote:
>
>> What you're looking for is a way to re-try requests in the case where the
>> server is unreachable, which is not something that HTTP or the browser
>> gives you automatically. If you had a proxy, but the server itself was
>> down, the proxy would likely return a 503 service unavailable status, which
>> the client could use to retry until the service was available (which might
>> only happen for a certain number of seconds or a certain number of tries).
>> It might also be possible for a proxy to wait and retry the upstream server
>> until it was available, but I can't think of a proxy right now with that
>> feature.
>>
>> HTTP itself doesn't have a timeout feature at all either. The timeout
>> that you're setting on the client side is a simple GWT Timer, if the
>> request hasn't finished (either in success or failure), it cancels the
>> upstream request and presents the failure you're seeing to the client.
>>
>> Be a little careful when implementing a retry mechanism, as it is
>> possible that the call made it to the server, and the server performed the
>> action, but the client lost internet connection while the response was on
>> its way to the client - that is, retrying a non-idempotent or expensive
>> action may cause problems you weren't expecting. A status code of 0 is
>> usually the client's way of saying "I wasn't able to get any reply from the
>> server for some reason" - taking that information and trying to do
>> something simple and idempotent until a server connection can be
>> reestablished lets you know that the server and network are both working
>> again, followed by some "did my last action succeed" before trying again
>> (or just let the user dismiss the message and try again) will help mitigate
>> this class of issues. A proxy sending back a 503 is a safer way to be sure
>> that the network connection is good, but only the server is down, so you
>> can retry - but be aware that technically there might be a network issue
>> between the proxy and server, though this is much less likely.
>>
>> Good luck,
>> Colin
>>
>> On Thursday, April 6, 2023 at 7:05:53 AM UTC-5 Dmitri wrote:
>>
>>> Dear Colin
>>>
>>> Thank you so much for your advice. I'll take a closer look at those
>>> areas.
>>>
>>> Just a little clarification: The server is not running at all. Both
>>> exceptions are generated from the client only with different timeout
>>> settings when it cannot reach the server.
>>> When the server is running - no problems in both cases. The purpose of
>>> the code is to make the client wait longer when the server is unreachable
>>> due to temporary communication problems.
>>>
>>> PS there are some typos in the codes I provide which I made when
>>> clean-up for posting., Please ignore them.
>>> Thank you again
>>>
>>> Best regards
>>> Dmitri
>>>
>>>
>>> On Thu, Apr 6, 2023 at 9:49 PM Colin Alworth wrote:
>>>
>>>> I believe you're experiencing different timeouts in different cases.
>>>> That is, the problem you're facing of a short timeout before you use your
>>>> RPC_TIMEOUT_MS is a server-side timeout (or potentially a proxy?), but
>>>> after you set a client-side timeout, the client is observing that the
>>>> server is taking too long, and terminating the call from its side,
>>>> resulting in the RequestTimeoutException.
>>>>
>>>> To confirm this, try setting the client-side timeout to something like
>>>> one minute, 60_000, and see that the error returns to the old message you
>>>> were seeing. A timeout set like this does not guarantee that the server
>&g
Re: Question about setting GWT RPC timeout
Hi all, I came across this thread, I have searched if there is some "global" request timeout that we can set on a RPC calls, not RequestBuilder, but the one from RemoteService created via GWT.create(service) ? I coudnt find anything, any idea? Tnx On Thursday, April 6, 2023 at 2:16:47 PM UTC+2 Colin Alworth wrote: > What you're looking for is a way to re-try requests in the case where the > server is unreachable, which is not something that HTTP or the browser > gives you automatically. If you had a proxy, but the server itself was > down, the proxy would likely return a 503 service unavailable status, which > the client could use to retry until the service was available (which might > only happen for a certain number of seconds or a certain number of tries). > It might also be possible for a proxy to wait and retry the upstream server > until it was available, but I can't think of a proxy right now with that > feature. > > HTTP itself doesn't have a timeout feature at all either. The timeout that > you're setting on the client side is a simple GWT Timer, if the request > hasn't finished (either in success or failure), it cancels the upstream > request and presents the failure you're seeing to the client. > > Be a little careful when implementing a retry mechanism, as it is possible > that the call made it to the server, and the server performed the action, > but the client lost internet connection while the response was on its way > to the client - that is, retrying a non-idempotent or expensive action may > cause problems you weren't expecting. A status code of 0 is usually the > client's way of saying "I wasn't able to get any reply from the server for > some reason" - taking that information and trying to do something simple > and idempotent until a server connection can be reestablished lets you know > that the server and network are both working again, followed by some "did > my last action succeed" before trying again (or just let the user dismiss > the message and try again) will help mitigate this class of issues. A proxy > sending back a 503 is a safer way to be sure that the network connection is > good, but only the server is down, so you can retry - but be aware that > technically there might be a network issue between the proxy and server, > though this is much less likely. > > Good luck, > Colin > > On Thursday, April 6, 2023 at 7:05:53 AM UTC-5 Dmitri wrote: > >> Dear Colin >> >> Thank you so much for your advice. I'll take a closer look at those areas. >> >> Just a little clarification: The server is not running at all. Both >> exceptions are generated from the client only with different timeout >> settings when it cannot reach the server. >> When the server is running - no problems in both cases. The purpose of >> the code is to make the client wait longer when the server is unreachable >> due to temporary communication problems. >> >> PS there are some typos in the codes I provide which I made when clean-up >> for posting., Please ignore them. >> Thank you again >> >> Best regards >> Dmitri >> >> >> On Thu, Apr 6, 2023 at 9:49 PM Colin Alworth wrote: >> >>> I believe you're experiencing different timeouts in different cases. >>> That is, the problem you're facing of a short timeout before you use your >>> RPC_TIMEOUT_MS is a server-side timeout (or potentially a proxy?), but >>> after you set a client-side timeout, the client is observing that the >>> server is taking too long, and terminating the call from its side, >>> resulting in the RequestTimeoutException. >>> >>> To confirm this, try setting the client-side timeout to something like >>> one minute, 60_000, and see that the error returns to the old message you >>> were seeing. A timeout set like this does not guarantee that the server >>> stops processing the request, only that the client stops waiting for it, >>> and it may not be appropriate for your use case at all. >>> >>> With the client-side timeout set to a reasonable amount or entirely >>> removed, take a closer look at the error message you're getting from the >>> server, and any server or proxy logs you're getting. If there is a proxy, >>> see if you can connect directly to the server to rule out the proxy setting >>> this short timeout. Very likely this is a configuration on the server/proxy >>> that can be change to suit your requirements. >>> >>> On Thursday, April 6, 2023 at 2:26:31 AM UTC-5 Dmitri wrote: >>> >>>> Dear gurus, >>>> >&
Re: gwt-maven-springboot-archetype updated ...
Thanks Thomas. Now switched to: -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 [image: Screen.png] Which also works great. On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote: > You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather than > the legacy -Xdebug -Xrunjdwp (and then you no longer need the quotes ) > > And when I say legacy, I really mean it: already in Java 8 -Xdebug does > nothing ( > https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) > > and Xrunjdwp is superceded by agentlib ( > https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG > ) > > On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 > ma...@craig-mitchell.com wrote: > >> Thank you! Working great now (quotes were important). >> >> [image: Screen.png] >> >> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote: >> >>> Mmmh, it might be worth adding this information to the archetype docs. >>> >>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6429293d-9a59-427a-b627-aadb2f3c75c5n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather than the legacy -Xdebug -Xrunjdwp (and then you no longer need the quotes ) And when I say legacy, I really mean it: already in Java 8 -Xdebug does nothing (https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI) and Xrunjdwp is superceded by agentlib (https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG) On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 ma...@craig-mitchell.com wrote: > Thank you! Working great now (quotes were important). > > [image: Screen.png] > > On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote: > >> Mmmh, it might be worth adding this information to the archetype docs. >> >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/439e71d0-62d2-4f59-b378-e37ae1769dd2n%40googlegroups.com.
Re: GWT Eclipse Plugin 4 Problem
There is a pending patch for this at https://github.com/gwt-plugins/gwt-eclipse-plugin/pull/475. You should be able to pull and build this to get working again on the very latest Eclipse versions - and if you do, leave a comment, a code review, etc, and we can get this merged more expediently. GWT is largely a volunteer project, the GWT Plugin for Eclipse doubly so - and while the GWT contributor pool is small, the GPE pool is more of a puddle. We're trying to raise interest in this among users and contributors, but we can't drag people to work on code or force them to pay for work to get done. The GPE tooling has never formally been part of the GWT project (first owned entirely by the App Engine team at Google if I'm not mistaken, then ran as its own github org for many years), but we're trying to bring these pieces in line as we grow. Additionally, Eclipse marketshare isn't what it once was - I can't remember the last time I saw a project that ran better on Eclipse than IntelliJ. This is not intended as a slight towards anyone who is more productive with Eclipse, only as a remark that with fewer interest, it is hard to keep the project going. Finally, the workaround is straightforward - 2023-09 was the latest as of 60 days ago, falling back to it will likely not destroy any development workflows. On Wednesday, January 31, 2024 at 8:09:53 PM UTC-6 Fred Andrews wrote: > No response to this man's issue after 6 weeks and I just hit the same > problem. This is shocking. > > The plugin cannot be installed. Is GWT a dead product? > > On Monday, December 11, 2023 at 2:12:30 PM UTC-6 Bob Lacatena wrote: > >> Hey. My coworker and I ran into trouble installing the GWT plugin on >> Eclipse 2023-12 (worked fine on 2023-09, so this isn't urgent, I'm just >> letting you know). >> >> A couple of weeks ago I got a new Mac, installed Eclipse 2023-09 and the >> GWT plugin, no problem. >> >> My coworker just got a new PC (Windows 11), and got Eclipse 2023-12 (just >> released), tried to install the GWT plugin as I did, and could not. It >> first required JustJ Adoptium OpenJDK 21. >> >> JustJ Adoptium OpenJDK Hotspot JRE Complete 21.0.1.v20231028-0937 >> org.eclipse.justj.openjdk.hotspot.jre.full.feature.group Eclipse JustJ >> >> After doing so, getting the GWT plugin still failed. First it says >> "Cannot complete operation. Computing alternate solutions, may take a >> while: X/15" >> >> Then it tells you it failed, giving you a chance to select other features >> (but there is only one). >> >> I confirmed that this also happens with 2023-12 on my Mac. >> >> My co-worker dropped back to 2023-09 on his PC, and it installed fine. >> >> Just an FYI. >> >> >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/d7165f83-d53f-44dd-8996-4dc76a0418fen%40googlegroups.com.
Re: GWT Eclipse Plugin 4 Problem
No response to this man's issue after 6 weeks and I just hit the same problem. This is shocking. The plugin cannot be installed. Is GWT a dead product? On Monday, December 11, 2023 at 2:12:30 PM UTC-6 Bob Lacatena wrote: > Hey. My coworker and I ran into trouble installing the GWT plugin on > Eclipse 2023-12 (worked fine on 2023-09, so this isn't urgent, I'm just > letting you know). > > A couple of weeks ago I got a new Mac, installed Eclipse 2023-09 and the > GWT plugin, no problem. > > My coworker just got a new PC (Windows 11), and got Eclipse 2023-12 (just > released), tried to install the GWT plugin as I did, and could not. It > first required JustJ Adoptium OpenJDK 21. > > JustJ Adoptium OpenJDK Hotspot JRE Complete 21.0.1.v20231028-0937 > org.eclipse.justj.openjdk.hotspot.jre.full.feature.group Eclipse JustJ > > After doing so, getting the GWT plugin still failed. First it says > "Cannot complete operation. Computing alternate solutions, may take a > while: X/15" > > Then it tells you it failed, giving you a chance to select other features > (but there is only one). > > I confirmed that this also happens with 2023-12 on my Mac. > > My co-worker dropped back to 2023-09 on his PC, and it installed fine. > > Just an FYI. > > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4ad3ac71-5a9a-49b7-b064-90a930814287n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Thank you! Working great now (quotes were important). [image: Screen.png] On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote: > Mmmh, it might be worth adding this information to the archetype docs. > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/9b1b1eac-276b-41ba-affd-cfb2d57e64c8n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Mmmh, it might be worth adding this information to the archetype docs. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/c06bb811-3011-4211-981f-034d333bf52bn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Mmmh, might be worse adding this information to the archetype read me. Frank Hossfeld schrieb am Mittwoch, 31. Januar 2024 um 20:35:40 UTC+1: > Thanks, I am usually using the Spring Boot run configuration from > IntelliJ. This works without additional parameters. > > bbe...@gmail.com schrieb am Mittwoch, 31. Januar 2024 um 19:12:22 UTC+1: > >> The problem is that spring-boot:run is going to launch another Java >> process for you application, so mvnDebug is attached to the first Maven >> process, not your application. >> >> You will need to execute spring-boot:run passing the config to enable >> remote debugging: >> >> mvn spring-boot:run -pl your-project >> "-Dspring-boot.run.jvmArguments=-Xdebug >> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000" >> >> On Wednesday 31 January 2024 at 08:57:08 UTC-5 Frank Hossfeld wrote: >> >>> Hi, >>> >>> in case using the Ultimate Edition, and have the Spring Developers >>> Plugin installed, just select the Application file and click the green >>> triangle. >>> >>> In both edition creating a Maven run configuration should also work. >>> >>> [image: rc-spring-boot.png] >>> >>> >>> Craig Mitchell schrieb am Mittwoch, 31. Januar 2024 um 13:00:43 UTC+1: >>> >>>> Hi, >>>> >>>> I'm able to debug the GWT client okay (in Chrome). However, debugging >>>> the SpringBoot server in IntelliJ isn't working. >>>> >>>> I already have the code server running, and then I start the server >>>> with: >>>> >>>> mvnDebug spring-boot:run -pl mywebapp-server -am >>>> >>>> The server then waits for the debugger to attach, so I start up a >>>> remote JVM debug in IntelliJ: >>>> >>>> [image: Screen.png] >>>> >>>> And it attaches to the server, which then triggers the server to >>>> continue its start. >>>> >>>> Everything is now up and running great. >>>> >>>> However, putting breakpoints in the server code in IntelliJ, the >>>> breakpoints never get hit. Any suggestions as to why? >>>> >>>> This might not be a GWT issue, so apologies if it isn't. >>>> >>>> Thanks. >>>> >>>> On Thursday 25 January 2024 at 5:55:48 pm UTC+11 Ralph Fiergolla wrote: >>>> >>>>> Finally! Thanks a lot! >>>>> >>>>> Thomas Broyer schrieb am Mi. 24. Jan. 2024 um >>>>> 19:57: >>>>> >>>>>> oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at >>>>>> least Java 11. >>>>>> >>>>>> On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer >>>>>> wrote: >>>>>> >>>>>>> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 >>>>>>> (in version 2024.1.24) >>>>>>> >>>>>>> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 >>>>>>> ma...@craig-mitchell.com wrote: >>>>>>> >>>>>>>> Ignore my post. Just realised the doco uses >>>>>>>> net.ltgt.gwt.archetypes and not the springboot >>>>>>>> com.github.nalukit.archetype. >>>>>>>> >>>>>>>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta >>>>>>>> stuff. >>>>>>>> >>>>>>>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I was going to suggest the GWT doco gets updated to use this, but >>>>>>>>> I see you already have! >>>>>>>>> https://www.gwtproject.org/gettingstarted-v2.html >>>>>>>>> >>>>>>>>> Excellent stuff! >>>>>>>>> >>>>>>>>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> both archetypes have been updated to the latest GWT (2.11.0) & >>>>>>>>>> Spring Boot version (3.2.2). >>>>>>&
Re: gwt-maven-springboot-archetype updated ...
Thanks, I am usually using the Spring Boot run configuration from IntelliJ. This works without additional parameters. bbe...@gmail.com schrieb am Mittwoch, 31. Januar 2024 um 19:12:22 UTC+1: > The problem is that spring-boot:run is going to launch another Java > process for you application, so mvnDebug is attached to the first Maven > process, not your application. > > You will need to execute spring-boot:run passing the config to enable > remote debugging: > > mvn spring-boot:run -pl your-project > "-Dspring-boot.run.jvmArguments=-Xdebug > -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000" > > On Wednesday 31 January 2024 at 08:57:08 UTC-5 Frank Hossfeld wrote: > >> Hi, >> >> in case using the Ultimate Edition, and have the Spring Developers Plugin >> installed, just select the Application file and click the green triangle. >> >> In both edition creating a Maven run configuration should also work. >> >> [image: rc-spring-boot.png] >> >> >> Craig Mitchell schrieb am Mittwoch, 31. Januar 2024 um 13:00:43 UTC+1: >> >>> Hi, >>> >>> I'm able to debug the GWT client okay (in Chrome). However, debugging >>> the SpringBoot server in IntelliJ isn't working. >>> >>> I already have the code server running, and then I start the server with: >>> >>> mvnDebug spring-boot:run -pl mywebapp-server -am >>> >>> The server then waits for the debugger to attach, so I start up a remote >>> JVM debug in IntelliJ: >>> >>> [image: Screen.png] >>> >>> And it attaches to the server, which then triggers the server to >>> continue its start. >>> >>> Everything is now up and running great. >>> >>> However, putting breakpoints in the server code in IntelliJ, the >>> breakpoints never get hit. Any suggestions as to why? >>> >>> This might not be a GWT issue, so apologies if it isn't. >>> >>> Thanks. >>> >>> On Thursday 25 January 2024 at 5:55:48 pm UTC+11 Ralph Fiergolla wrote: >>> >>>> Finally! Thanks a lot! >>>> >>>> Thomas Broyer schrieb am Mi. 24. Jan. 2024 um >>>> 19:57: >>>> >>>>> oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at >>>>> least Java 11. >>>>> >>>>> On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote: >>>>> >>>>>> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in >>>>>> version 2024.1.24) >>>>>> >>>>>> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 >>>>>> ma...@craig-mitchell.com wrote: >>>>>> >>>>>>> Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes >>>>>>> and not the springboot com.github.nalukit.archetype. >>>>>>> >>>>>>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta >>>>>>> stuff. >>>>>>> >>>>>>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell >>>>>>> wrote: >>>>>>> >>>>>>>> I was going to suggest the GWT doco gets updated to use this, but I >>>>>>>> see you already have! >>>>>>>> https://www.gwtproject.org/gettingstarted-v2.html >>>>>>>> >>>>>>>> Excellent stuff! >>>>>>>> >>>>>>>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> both archetypes have been updated to the latest GWT (2.11.0) & >>>>>>>>> Spring Boot version (3.2.2). >>>>>>>>> Happy generating ... >>>>>>>>> >>>>>>>>> cu Frank >>>>>>>>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 >>>>>>>>> UTC+1: >>>>>>>>> >>>>>>>>>> Hi Grayson, >>>>>>>>>> >>>>>>>>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is >>>>>>>>>> released. I'll try to take a look today. >>>>>>>>>> >&g
Re: gwt-maven-springboot-archetype updated ...
The problem is that spring-boot:run is going to launch another Java process for you application, so mvnDebug is attached to the first Maven process, not your application. You will need to execute spring-boot:run passing the config to enable remote debugging: mvn spring-boot:run -pl your-project "-Dspring-boot.run.jvmArguments=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000" On Wednesday 31 January 2024 at 08:57:08 UTC-5 Frank Hossfeld wrote: > Hi, > > in case using the Ultimate Edition, and have the Spring Developers Plugin > installed, just select the Application file and click the green triangle. > > In both edition creating a Maven run configuration should also work. > > [image: rc-spring-boot.png] > > > Craig Mitchell schrieb am Mittwoch, 31. Januar 2024 um 13:00:43 UTC+1: > >> Hi, >> >> I'm able to debug the GWT client okay (in Chrome). However, debugging >> the SpringBoot server in IntelliJ isn't working. >> >> I already have the code server running, and then I start the server with: >> >> mvnDebug spring-boot:run -pl mywebapp-server -am >> >> The server then waits for the debugger to attach, so I start up a remote >> JVM debug in IntelliJ: >> >> [image: Screen.png] >> >> And it attaches to the server, which then triggers the server to continue >> its start. >> >> Everything is now up and running great. >> >> However, putting breakpoints in the server code in IntelliJ, the >> breakpoints never get hit. Any suggestions as to why? >> >> This might not be a GWT issue, so apologies if it isn't. >> >> Thanks. >> >> On Thursday 25 January 2024 at 5:55:48 pm UTC+11 Ralph Fiergolla wrote: >> >>> Finally! Thanks a lot! >>> >>> Thomas Broyer schrieb am Mi. 24. Jan. 2024 um 19:57: >>> >>>> oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at >>>> least Java 11. >>>> >>>> On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote: >>>> >>>>> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in >>>>> version 2024.1.24) >>>>> >>>>> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 >>>>> ma...@craig-mitchell.com wrote: >>>>> >>>>>> Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes >>>>>> and not the springboot com.github.nalukit.archetype. >>>>>> >>>>>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta >>>>>> stuff. >>>>>> >>>>>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell >>>>>> wrote: >>>>>> >>>>>>> I was going to suggest the GWT doco gets updated to use this, but I >>>>>>> see you already have! >>>>>>> https://www.gwtproject.org/gettingstarted-v2.html >>>>>>> >>>>>>> Excellent stuff! >>>>>>> >>>>>>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> both archetypes have been updated to the latest GWT (2.11.0) & >>>>>>>> Spring Boot version (3.2.2). >>>>>>>> Happy generating ... >>>>>>>> >>>>>>>> cu Frank >>>>>>>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: >>>>>>>> >>>>>>>>> Hi Grayson, >>>>>>>>> >>>>>>>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. >>>>>>>>> I'll try to take a look today. >>>>>>>>> >>>>>>>>> cu Frank >>>>>>>>> >>>>>>>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 >>>>>>>>> UTC+1: >>>>>>>>> >>>>>>>>>> Hi Frank, >>>>>>>>>> >>>>>>>>>> Would you please also publish the new version for >>>>>>>>>> "modular-springboot-webapp" (the one that generates a gwt project >>>>>>>>>> with >>>>>>>>>> sa
Re: gwt-maven-springboot-archetype updated ...
Hi, I'm able to debug the GWT client okay (in Chrome). However, debugging the SpringBoot server in IntelliJ isn't working. I already have the code server running, and then I start the server with: mvnDebug spring-boot:run -pl mywebapp-server -am The server then waits for the debugger to attach, so I start up a remote JVM debug in IntelliJ: [image: Screen.png] And it attaches to the server, which then triggers the server to continue its start. Everything is now up and running great. However, putting breakpoints in the server code in IntelliJ, the breakpoints never get hit. Any suggestions as to why? This might not be a GWT issue, so apologies if it isn't. Thanks. On Thursday 25 January 2024 at 5:55:48 pm UTC+11 Ralph Fiergolla wrote: > Finally! Thanks a lot! > > Thomas Broyer schrieb am Mi. 24. Jan. 2024 um 19:57: > >> oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at least >> Java 11. >> >> On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote: >> >>> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in >>> version 2024.1.24) >>> >>> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 >>> ma...@craig-mitchell.com wrote: >>> >>>> Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes >>>> and not the springboot com.github.nalukit.archetype. >>>> >>>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta >>>> stuff. >>>> >>>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote: >>>> >>>>> I was going to suggest the GWT doco gets updated to use this, but I >>>>> see you already have! >>>>> https://www.gwtproject.org/gettingstarted-v2.html >>>>> >>>>> Excellent stuff! >>>>> >>>>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> both archetypes have been updated to the latest GWT (2.11.0) & Spring >>>>>> Boot version (3.2.2). >>>>>> Happy generating ... >>>>>> >>>>>> cu Frank >>>>>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: >>>>>> >>>>>>> Hi Grayson, >>>>>>> >>>>>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. >>>>>>> I'll try to take a look today. >>>>>>> >>>>>>> cu Frank >>>>>>> >>>>>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 >>>>>>> UTC+1: >>>>>>> >>>>>>>> Hi Frank, >>>>>>>> >>>>>>>> Would you please also publish the new version for >>>>>>>> "modular-springboot-webapp" (the one that generates a gwt project with >>>>>>>> sample code)? The lastest verison of "modular-springboot-webapp" is >>>>>>>> still " >>>>>>>> 2022.9.14 >>>>>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >>>>>>>> >>>>>>>> which is more than a year old. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Grayson >>>>>>>> >>>>>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld >>>>>>>> wrote: >>>>>>>> >>>>>>>> Happy new year! I just released a new version of the >>>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >>>>>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java >>>>>>>> 17) >>>>>>>> with GWT 2.10.0 multi module project. Happy coding! >>>>>>>> >>>>>>>> -- >> You received this message because you are subscribed to the Google Groups >> "GWT Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to google-web-tool...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-web-toolkit/0c06d897-5654-49d8-871a-f10d8ea2d171n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-web-toolkit/0c06d897-5654-49d8-871a-f10d8ea2d171n%40googlegroups.com?utm_medium=email_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4574c03c-8a5f-44f3-9b4b-8cab305e491cn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Finally! Thanks a lot! Thomas Broyer schrieb am Mi. 24. Jan. 2024 um 19:57: > oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at least > Java 11. > > On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote: > >> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in >> version 2024.1.24) >> >> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 >> ma...@craig-mitchell.com wrote: >> >>> Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes >>> and not the springboot com.github.nalukit.archetype. >>> >>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta >>> stuff. >>> >>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote: >>> >>>> I was going to suggest the GWT doco gets updated to use this, but I see >>>> you already have! https://www.gwtproject.org/gettingstarted-v2.html >>>> >>>> Excellent stuff! >>>> >>>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote: >>>> >>>>> Hi, >>>>> >>>>> both archetypes have been updated to the latest GWT (2.11.0) & Spring >>>>> Boot version (3.2.2). >>>>> Happy generating ... >>>>> >>>>> cu Frank >>>>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: >>>>> >>>>>> Hi Grayson, >>>>>> >>>>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. >>>>>> I'll try to take a look today. >>>>>> >>>>>> cu Frank >>>>>> >>>>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 >>>>>> UTC+1: >>>>>> >>>>>>> Hi Frank, >>>>>>> >>>>>>> Would you please also publish the new version for >>>>>>> "modular-springboot-webapp" (the one that generates a gwt project with >>>>>>> sample code)? The lastest verison of "modular-springboot-webapp" is >>>>>>> still " >>>>>>> 2022.9.14 >>>>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >>>>>>> which is more than a year old. >>>>>>> >>>>>>> Thanks, >>>>>>> Grayson >>>>>>> >>>>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: >>>>>>> >>>>>>> Happy new year! I just released a new version of the >>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >>>>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) >>>>>>> with GWT 2.10.0 multi module project. Happy coding! >>>>>>> >>>>>>> -- > You received this message because you are subscribed to the Google Groups > "GWT Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-web-toolkit+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit/0c06d897-5654-49d8-871a-f10d8ea2d171n%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit/0c06d897-5654-49d8-871a-f10d8ea2d171n%40googlegroups.com?utm_medium=email_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CACwwWxNg6bbc7Pd%3D823Dd24apHGfmboNgZ_%3Dh-1Q7O%3Dx8tLZjw%40mail.gmail.com.
Re: gwt-maven-springboot-archetype updated ...
Awesome stuff! Thank you both. Makes starting a new GWT project a breeze! On Thursday 25 January 2024 at 6:08:27 am UTC+11 Frank Hossfeld wrote: > Thanks! > > Thomas Broyer schrieb am Mittwoch, 24. Januar 2024 um 19:57:12 UTC+1: > >> oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at least >> Java 11. >> >> On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote: >> >>> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in >>> version 2024.1.24) >>> >>> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 >>> ma...@craig-mitchell.com wrote: >>> >>>> Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes >>>> and not the springboot com.github.nalukit.archetype. >>>> >>>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta >>>> stuff. >>>> >>>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote: >>>> >>>>> I was going to suggest the GWT doco gets updated to use this, but I >>>>> see you already have! >>>>> https://www.gwtproject.org/gettingstarted-v2.html >>>>> >>>>> Excellent stuff! >>>>> >>>>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> both archetypes have been updated to the latest GWT (2.11.0) & Spring >>>>>> Boot version (3.2.2). >>>>>> Happy generating ... >>>>>> >>>>>> cu Frank >>>>>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: >>>>>> >>>>>>> Hi Grayson, >>>>>>> >>>>>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. >>>>>>> I'll try to take a look today. >>>>>>> >>>>>>> cu Frank >>>>>>> >>>>>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 >>>>>>> UTC+1: >>>>>>> >>>>>>>> Hi Frank, >>>>>>>> >>>>>>>> Would you please also publish the new version for >>>>>>>> "modular-springboot-webapp" (the one that generates a gwt project with >>>>>>>> sample code)? The lastest verison of "modular-springboot-webapp" is >>>>>>>> still " >>>>>>>> 2022.9.14 >>>>>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >>>>>>>> >>>>>>>> which is more than a year old. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Grayson >>>>>>>> >>>>>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld >>>>>>>> wrote: >>>>>>>> >>>>>>>> Happy new year! I just released a new version of the >>>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >>>>>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java >>>>>>>> 17) >>>>>>>> with GWT 2.10.0 multi module project. Happy coding! >>>>>>>> >>>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/41cd4bba-4cab-4883-8864-7c37bff163ben%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Thanks! Thomas Broyer schrieb am Mittwoch, 24. Januar 2024 um 19:57:12 UTC+1: > oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at least > Java 11. > > On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote: > >> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in >> version 2024.1.24) >> >> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 >> ma...@craig-mitchell.com wrote: >> >>> Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes >>> and not the springboot com.github.nalukit.archetype. >>> >>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta >>> stuff. >>> >>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote: >>> >>>> I was going to suggest the GWT doco gets updated to use this, but I see >>>> you already have! https://www.gwtproject.org/gettingstarted-v2.html >>>> >>>> Excellent stuff! >>>> >>>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote: >>>> >>>>> Hi, >>>>> >>>>> both archetypes have been updated to the latest GWT (2.11.0) & Spring >>>>> Boot version (3.2.2). >>>>> Happy generating ... >>>>> >>>>> cu Frank >>>>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: >>>>> >>>>>> Hi Grayson, >>>>>> >>>>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. >>>>>> I'll try to take a look today. >>>>>> >>>>>> cu Frank >>>>>> >>>>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 >>>>>> UTC+1: >>>>>> >>>>>>> Hi Frank, >>>>>>> >>>>>>> Would you please also publish the new version for >>>>>>> "modular-springboot-webapp" (the one that generates a gwt project with >>>>>>> sample code)? The lastest verison of "modular-springboot-webapp" is >>>>>>> still " >>>>>>> 2022.9.14 >>>>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >>>>>>> >>>>>>> which is more than a year old. >>>>>>> >>>>>>> Thanks, >>>>>>> Grayson >>>>>>> >>>>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: >>>>>>> >>>>>>> Happy new year! I just released a new version of the >>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >>>>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) >>>>>>> with GWT 2.10.0 multi module project. Happy coding! >>>>>>> >>>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/374d671a-973a-4b8e-b784-fbfd7eba0993n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at least Java 11. On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote: > I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in > version 2024.1.24) > > On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 > ma...@craig-mitchell.com wrote: > >> Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes and >> not the springboot com.github.nalukit.archetype. >> >> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta stuff. >> >> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote: >> >>> I was going to suggest the GWT doco gets updated to use this, but I see >>> you already have! https://www.gwtproject.org/gettingstarted-v2.html >>> >>> Excellent stuff! >>> >>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote: >>> >>>> Hi, >>>> >>>> both archetypes have been updated to the latest GWT (2.11.0) & Spring >>>> Boot version (3.2.2). >>>> Happy generating ... >>>> >>>> cu Frank >>>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: >>>> >>>>> Hi Grayson, >>>>> >>>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. >>>>> I'll try to take a look today. >>>>> >>>>> cu Frank >>>>> >>>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 >>>>> UTC+1: >>>>> >>>>>> Hi Frank, >>>>>> >>>>>> Would you please also publish the new version for >>>>>> "modular-springboot-webapp" (the one that generates a gwt project with >>>>>> sample code)? The lastest verison of "modular-springboot-webapp" is >>>>>> still " >>>>>> 2022.9.14 >>>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >>>>>> >>>>>> which is more than a year old. >>>>>> >>>>>> Thanks, >>>>>> Grayson >>>>>> >>>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: >>>>>> >>>>>> Happy new year! I just released a new version of the >>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >>>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) >>>>>> with GWT 2.10.0 multi module project. Happy coding! >>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/0c06d897-5654-49d8-871a-f10d8ea2d171n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in version 2024.1.24) On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 ma...@craig-mitchell.com wrote: > Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes and > not the springboot com.github.nalukit.archetype. > > And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta stuff. > > On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote: > >> I was going to suggest the GWT doco gets updated to use this, but I see >> you already have! https://www.gwtproject.org/gettingstarted-v2.html >> >> Excellent stuff! >> >> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote: >> >>> Hi, >>> >>> both archetypes have been updated to the latest GWT (2.11.0) & Spring >>> Boot version (3.2.2). >>> Happy generating ... >>> >>> cu Frank >>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: >>> >>>> Hi Grayson, >>>> >>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. I'll >>>> try to take a look today. >>>> >>>> cu Frank >>>> >>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 >>>> UTC+1: >>>> >>>>> Hi Frank, >>>>> >>>>> Would you please also publish the new version for >>>>> "modular-springboot-webapp" (the one that generates a gwt project with >>>>> sample code)? The lastest verison of "modular-springboot-webapp" is still >>>>> " >>>>> 2022.9.14 >>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >>>>> >>>>> which is more than a year old. >>>>> >>>>> Thanks, >>>>> Grayson >>>>> >>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: >>>>> >>>>> Happy new year! I just released a new version of the >>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) >>>>> with GWT 2.10.0 multi module project. Happy coding! >>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6e456dea-abb4-4ffc-b8e8-9fc12c7ab3bcn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Yeap, that's right. Needs an update. May be I'll create a PR ... At the end of the https://www.gwtproject.org/gettingstarted-v2.html site, you will find a link to the springboot-archetype. Craig Mitchell schrieb am Mittwoch, 24. Januar 2024 um 10:58:45 UTC+1: > Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes and > not the springboot com.github.nalukit.archetype. > > And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta stuff. > > On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote: > >> I was going to suggest the GWT doco gets updated to use this, but I see >> you already have! https://www.gwtproject.org/gettingstarted-v2.html >> >> Excellent stuff! >> >> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote: >> >>> Hi, >>> >>> both archetypes have been updated to the latest GWT (2.11.0) & Spring >>> Boot version (3.2.2). >>> Happy generating ... >>> >>> cu Frank >>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: >>> >>>> Hi Grayson, >>>> >>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. I'll >>>> try to take a look today. >>>> >>>> cu Frank >>>> >>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 >>>> UTC+1: >>>> >>>>> Hi Frank, >>>>> >>>>> Would you please also publish the new version for >>>>> "modular-springboot-webapp" (the one that generates a gwt project with >>>>> sample code)? The lastest verison of "modular-springboot-webapp" is still >>>>> " >>>>> 2022.9.14 >>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >>>>> >>>>> which is more than a year old. >>>>> >>>>> Thanks, >>>>> Grayson >>>>> >>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: >>>>> >>>>> Happy new year! I just released a new version of the >>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) >>>>> with GWT 2.10.0 multi module project. Happy coding! >>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/61af60f0-c4ed-4c43-9218-a671588a317cn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Ignore my post. Just realised the doco uses net.ltgt.gwt.archetypes and not the springboot com.github.nalukit.archetype. And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta stuff. On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote: > I was going to suggest the GWT doco gets updated to use this, but I see > you already have! https://www.gwtproject.org/gettingstarted-v2.html > > Excellent stuff! > > On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote: > >> Hi, >> >> both archetypes have been updated to the latest GWT (2.11.0) & Spring >> Boot version (3.2.2). >> Happy generating ... >> >> cu Frank >> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: >> >>> Hi Grayson, >>> >>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. I'll >>> try to take a look today. >>> >>> cu Frank >>> >>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 UTC+1: >>> >>>> Hi Frank, >>>> >>>> Would you please also publish the new version for >>>> "modular-springboot-webapp" (the one that generates a gwt project with >>>> sample code)? The lastest verison of "modular-springboot-webapp" is still " >>>> 2022.9.14 >>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >>>> >>>> which is more than a year old. >>>> >>>> Thanks, >>>> Grayson >>>> >>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: >>>> >>>> Happy new year! I just released a new version of the >>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) >>>> with GWT 2.10.0 multi module project. Happy coding! >>>> >>>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/29f805cb-ac40-4bd5-86f3-0cd5d78c1d83n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
I was going to suggest the GWT doco gets updated to use this, but I see you already have! https://www.gwtproject.org/gettingstarted-v2.html Excellent stuff! On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote: > Hi, > > both archetypes have been updated to the latest GWT (2.11.0) & Spring Boot > version (3.2.2). > Happy generating ... > > cu Frank > Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: > >> Hi Grayson, >> >> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. I'll >> try to take a look today. >> >> cu Frank >> >> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 UTC+1: >> >>> Hi Frank, >>> >>> Would you please also publish the new version for >>> "modular-springboot-webapp" (the one that generates a gwt project with >>> sample code)? The lastest verison of "modular-springboot-webapp" is still " >>> 2022.9.14 >>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >>> >>> which is more than a year old. >>> >>> Thanks, >>> Grayson >>> >>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: >>> >>> Happy new year! I just released a new version of the >>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) >>> with GWT 2.10.0 multi module project. Happy coding! >>> >>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/5b539b3c-18fc-4c3b-a573-a8a48c1bcf3an%40googlegroups.com.
Re: [gwt-contrib] Re: Infinite loop at compile time
Thanks Colin. I should have looked at the issue tracker. Sorry about that.
On Mon, Jan 22, 2024 at 5:01 PM Colin Alworth wrote:
> Thanks for reporting - perhaps better for the bug tracker, and indeed we
> do this (or something like it) filed already, see
> https://github.com/gwtproject/gwt/issues/9840.
>
> Your email title says that this is a compile time infinite loop, but then
> the body suggests that it was a runtime error. If it were to be exhibited
> at runtime, it would almost certainly be a stackoverflow rather than
> looping forever (barring some sort of tail call optimization). The actual
> loop that you're seeing is waaay up the stack in
>
> at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.optimizeJsLoop(JavaToJavaScriptCompiler.java:1001)
>
> where the compiler decides to optimize until it reaches your optimization
> level, or until nothing changes. While SDM stands for "Super Dev Mode", it
> can also be understood to mean "Super Draft Mode", so the compiler builds
> as quickly and cheaply as possible, letting your app escape with very
> little optimization. This means that in SDM, you will not get stuck in this
> loop - the optimization loop won't run at all (see one frame up,
> shouldOptimize will return false), and you'll instead experience a
> stackoverflow at runtime.
>
> I didn't continue investigation of the problem further yet, but the linked
> ticket does have some analysis to consider.
> On Monday, January 22, 2024 at 8:30:50 AM UTC-6 Paul Robinson wrote:
>
>> I just found an infinite loop while running the GWT compiler.
>>
>> There was a trivial bug in my code which resulted in an infinite loop at
>> *runtime*. This is a method that was calling itself recursively. It was
>> inside a generic class, and the method had a single line that was something
>> like this:
>>
>> public class A extends C {
>> public static A getA(D d, E e, F f) {
>> return getA(d, e, null);
>> }
>> }
>>
>> I have been running in dev mode with it like this, but not hitting this
>> code so I didn't notice the infinite loop.
>>
>> Wanting to test GWT 2.11.0, I switched from GWT 2.10.0 and did a full GWT
>> compile. The interesting thing is that the GWT compile also hit an infinite
>> loop. Or rather, it was apparently infinite. I stopped it after 50 minutes,
>> where it would normally complete in about about 90 seconds. I dropped back
>> to 2.10.0, and found the same behaviour. So it's not caused by the new
>> release.
>>
>> Fixing the bug in my code meant it then compiled properly (in both 2.11.0
>> and 2.10.0).
>>
>> Is this interesting enough to warrant further investigation? This is code
>> inside a large application, so isolating a simple example that demonstrates
>> it might not work easily.
>>
>> FWIW there's a stack trace taken while stuck in the loop, compiling with
>> 2.11.0 here: https://pastebin.com/qckpswRD
>>
>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/58e74afc-7677-4a92-8895-880d884cd802n%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/58e74afc-7677-4a92-8895-880d884cd802n%40googlegroups.com?utm_medium=email_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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGHNWN%2Bej52aGjUnGKMMBKSjLiJCGQ_0Z1PtM6O2t_NoQHbXhg%40mail.gmail.com.
Re: gwt-maven-springboot-archetype updated ...
Hi, both archetypes have been updated to the latest GWT (2.11.0) & Spring Boot version (3.2.2). Happy generating ... cu Frank Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1: > Hi Grayson, > > it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. I'll > try to take a look today. > > cu Frank > > grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 UTC+1: > >> Hi Frank, >> >> Would you please also publish the new version for >> "modular-springboot-webapp" (the one that generates a gwt project with >> sample code)? The lastest verison of "modular-springboot-webapp" is still " >> 2022.9.14 >> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" >> >> which is more than a year old. >> >> Thanks, >> Grayson >> >> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: >> >> Happy new year! I just released a new version of the >> https://github.com/NaluKit/gwt-maven-springboot-archetype. The >> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) >> with GWT 2.10.0 multi module project. Happy coding! >> >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4455fae0-e3e7-4157-a98f-baacbdc77ce1n%40googlegroups.com.
[gwt-contrib] Re: Infinite loop at compile time
Thanks for reporting - perhaps better for the bug tracker, and indeed we do
this (or something like it) filed already, see
https://github.com/gwtproject/gwt/issues/9840.
Your email title says that this is a compile time infinite loop, but then
the body suggests that it was a runtime error. If it were to be exhibited
at runtime, it would almost certainly be a stackoverflow rather than
looping forever (barring some sort of tail call optimization). The actual
loop that you're seeing is waaay up the stack in
at
com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.optimizeJsLoop(JavaToJavaScriptCompiler.java:1001)
where the compiler decides to optimize until it reaches your optimization
level, or until nothing changes. While SDM stands for "Super Dev Mode", it
can also be understood to mean "Super Draft Mode", so the compiler builds
as quickly and cheaply as possible, letting your app escape with very
little optimization. This means that in SDM, you will not get stuck in this
loop - the optimization loop won't run at all (see one frame up,
shouldOptimize will return false), and you'll instead experience a
stackoverflow at runtime.
I didn't continue investigation of the problem further yet, but the linked
ticket does have some analysis to consider.
On Monday, January 22, 2024 at 8:30:50 AM UTC-6 Paul Robinson wrote:
> I just found an infinite loop while running the GWT compiler.
>
> There was a trivial bug in my code which resulted in an infinite loop at
> *runtime*. This is a method that was calling itself recursively. It was
> inside a generic class, and the method had a single line that was something
> like this:
>
> public class A extends C {
> public static A getA(D d, E e, F f) {
> return getA(d, e, null);
> }
> }
>
> I have been running in dev mode with it like this, but not hitting this
> code so I didn't notice the infinite loop.
>
> Wanting to test GWT 2.11.0, I switched from GWT 2.10.0 and did a full GWT
> compile. The interesting thing is that the GWT compile also hit an infinite
> loop. Or rather, it was apparently infinite. I stopped it after 50 minutes,
> where it would normally complete in about about 90 seconds. I dropped back
> to 2.10.0, and found the same behaviour. So it's not caused by the new
> release.
>
> Fixing the bug in my code meant it then compiled properly (in both 2.11.0
> and 2.10.0).
>
> Is this interesting enough to warrant further investigation? This is code
> inside a large application, so isolating a simple example that demonstrates
> it might not work easily.
>
> FWIW there's a stack trace taken while stuck in the loop, compiling with
> 2.11.0 here: https://pastebin.com/qckpswRD
>
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/58e74afc-7677-4a92-8895-880d884cd802n%40googlegroups.com.
[gwt-contrib] Infinite loop at compile time
I just found an infinite loop while running the GWT compiler.
There was a trivial bug in my code which resulted in an infinite loop at
*runtime*. This is a method that was calling itself recursively. It was
inside a generic class, and the method had a single line that was something
like this:
public class A extends C {
public static A getA(D d, E e, F f) {
return getA(d, e, null);
}
}
I have been running in dev mode with it like this, but not hitting this
code so I didn't notice the infinite loop.
Wanting to test GWT 2.11.0, I switched from GWT 2.10.0 and did a full GWT
compile. The interesting thing is that the GWT compile also hit an infinite
loop. Or rather, it was apparently infinite. I stopped it after 50 minutes,
where it would normally complete in about about 90 seconds. I dropped back
to 2.10.0, and found the same behaviour. So it's not caused by the new
release.
Fixing the bug in my code meant it then compiled properly (in both 2.11.0
and 2.10.0).
Is this interesting enough to warrant further investigation? This is code
inside a large application, so isolating a simple example that demonstrates
it might not work easily.
FWIW there's a stack trace taken while stuck in the loop, compiling with
2.11.0 here: https://pastebin.com/qckpswRD
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/e83dce79-9dd5-4985-9c86-9277e7261c25n%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Hi Grayson, it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. I'll try to take a look today. cu Frank grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 UTC+1: > Hi Frank, > > Would you please also publish the new version for > "modular-springboot-webapp" (the one that generates a gwt project with > sample code)? The lastest verison of "modular-springboot-webapp" is still " > 2022.9.14 > <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" > > which is more than a year old. > > Thanks, > Grayson > > On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: > > Happy new year! I just released a new version of the > https://github.com/NaluKit/gwt-maven-springboot-archetype. The > clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) > with GWT 2.10.0 multi module project. Happy coding! > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/66ec1efb-fe23-43a9-aa63-b9940823f5dbn%40googlegroups.com.
Re: gwt-maven-springboot-archetype updated ...
Hi Frank, Would you please also publish the new version for "modular-springboot-webapp" (the one that generates a gwt project with sample code)? The lastest verison of "modular-springboot-webapp" is still " 2022.9.14 <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>" which is more than a year old. Thanks, Grayson On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote: Happy new year! I just released a new version of the https://github.com/NaluKit/gwt-maven-springboot-archetype. The clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) with GWT 2.10.0 multi module project. Happy coding! -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/bab783b9-1880-438c-925a-ad39dc137cf3n%40googlegroups.com.
