Re: gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

> (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.

Re: gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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: Seeking Advice on Legacy Application Migration Strategy

['Frank Hossfeld' via GWT Users]

GWT 2.8.2 is pretty old - nearly seven years - and i am not sure, if the 
GWT 2.8.2 will work with Java 11

Migrating to the latest version of GWT will give you some benefits. IIRC 
GWT 2.8.2 generates at least 5 JS-files where GWT 2.11.0 only generates 2. 
This will speed up the build. Also, there is a security issue in older GWT 
versions (in case you are using RPC). 

To do so, separate your code in client-, shared- and server-modules (as 
Craig already mentioned).  Take a look 
here: https://github.com/tbroyer/gwt-maven-archetypes or 
here https://github.com/NaluKit/gwt-maven-springboot-archetype. This should 
give you an idea, how your project look like after the separation. Once 
done, it should be possible to use different Java versions on the client 
and server side.

Once you have separate your code, you can update the GWT version. My first 
step would be to update to GWT 2.10.0. I would do this, because to GWT 
2.10.0 works with the old javax stuff on the server side and give you the 
opportunity to patch GXT without updating the server stuff.  (IIRC you need 
to patch two classes). After the patch you can move to GWT 2.11.0 and Java 
11 and fix the other issues by updating versions, etc.

Wejden Mrabti schrieb am Freitag, 26. April 2024 um 09:12:33 UTC+2:

> thank you for your answer @craig Mitchell
> if i want to continue hibernate 6 , how to do launch gwt application on 
> java 11 ? 
> is it possible to continue working like this ? what do you think?
> Le vendredi 26 avril 2024 à 02:22:52 UTC+2, Craig Mitchell a écrit :
>
>> It'd be hard to answer that question, as we don't have all the details.  
>> As this is a GWT forum, I'd say, migrate GWT to the latest version first.  
>> But that might actually be bad advice, just depends on your project.
>>
>> My gut feel is you'd be best to decouple the front end and back end first.
>>
>> On Friday 26 April 2024 at 2:32:17 am UTC+10 Wejden Mrabti wrote:
>>
>>> Hello GWT Users 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 
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/a91eb3fa-af37-4c37-bc61-010bbd151763n%40googlegroups.com.

Re: Help to undrerstand how to use domino-jackson and the annotation JSONMapper

['Frank Hossfeld' via GWT Users]

Are you certain, that the annotation processor had ran?
I have not digged into domino-jackson, but I think, the @JsonMapper 
annotation triggers a annotation processor. The generated classes will be 
found under  'target/generated-sources/annotatins'

Marco Tenti (IoProgrammo88) schrieb am Montag, 15. April 2024 um 09:16:49 
UTC+2:

> The problem i cannot find the generate class "Person_MapperImpl" is under 
> the target folder somewhere ?
>
> Il giorno venerdì 12 aprile 2024 alle 18:25:30 UTC+2 Thomas Broyer ha 
> scritto:
>
>> Aren't you supposed to directly use the generated class rather than using 
>> GWT.create() ? (unless you also added a  in your gwt.xml)
>>
>> https://dominokit.com/solutions/domino-jackson/v1/docs/getting-started/quick-start
>>
>> On Friday, April 12, 2024 at 1:20:27 PM UTC+2 tenti...@gmail.com wrote:
>>
>>> I'm upgrading a old project and i want to replace the old gwt-jackson (
>>> https://dominokit.com/solutions/domino-jackson/v1)  with the 
>>> domino-jackson project (https://github.com/DominoKit/domino-jackson).
>>>
>>> It should be a simple transiction, but i cannot understand how to let 
>>> the GWT compilation "see" the implementations classes of the ObjectMapper 
>>> interface.
>>>
>>> *Here the "old" code from gwt-jackson*
>>>
>>> *public static interface AltriMetadatiDTOMapper extends 
>>> com.github.nmorel.gwtjackson.client.ObjectMapper>>
>>>  
>>> {} *
>>>
>>> * ... *
>>>
>>> * AltriMetadatiDTOMapper altriMetadatiDTOMapper = 
>>> GWT.create(AltriMetadatiDTOMapper.class); String jsonAltriMetadati = 
>>> altriMetadatiDTOMapper.write(object); *
>>>
>>> *Here the "new" code from domino-jackson*
>>> *@org.dominokit.jackson.annotation.JSONMapper public interface 
>>> AltriMetadatiDTOMapper extends 
>>> org.dominokit.jackson.ObjectMapper>> {}*
>>>
>>> * ... *
>>>
>>> * AltriMetadatiDTOMapper altriMetadatiDTOMapper = 
>>> GWT.create(AltriMetadatiDTOMappe.class); String jsonAltriMetadati = 
>>> altriMetadatiDTOMapper.write(object); *
>>>
>>> but it give to me this error
>>> [ERROR] Errors in 'xxx.java' [INFO] [ERROR] Line 662: Rebind result 
>>> 'xxx.AltriMetadatiDTOMapper' must be a class
>>>
>>> Did anyone know what i'm doing wrong ?
>>>
>>

-- 
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/b1089cf5-e4fc-4032-a588-b6bbb73a94dfn%40googlegroups.com.

Re: Help to undrerstand how to use domino-jackson and the annotation JSONMapper

['Frank Hossfeld' via GWT Users]

Are you certain, that the annotation processor already run?
I have not digged into domino-jackson, but I think, the @JsonMapper 
annotation triggers a annotation processor. The generated classes will be 
found under  'target/generated-sources/annotatins'


Marco Tenti (IoProgrammo88) schrieb am Montag, 15. April 2024 um 09:16:49 
UTC+2:

> The problem i cannot find the generate class "Person_MapperImpl" is under 
> the target folder somewhere ?
>
> Il giorno venerdì 12 aprile 2024 alle 18:25:30 UTC+2 Thomas Broyer ha 
> scritto:
>
>> Aren't you supposed to directly use the generated class rather than using 
>> GWT.create() ? (unless you also added a  in your gwt.xml)
>>
>> https://dominokit.com/solutions/domino-jackson/v1/docs/getting-started/quick-start
>>
>> On Friday, April 12, 2024 at 1:20:27 PM UTC+2 tenti...@gmail.com wrote:
>>
>>> I'm upgrading a old project and i want to replace the old gwt-jackson (
>>> https://dominokit.com/solutions/domino-jackson/v1)  with the 
>>> domino-jackson project (https://github.com/DominoKit/domino-jackson).
>>>
>>> It should be a simple transiction, but i cannot understand how to let 
>>> the GWT compilation "see" the implementations classes of the ObjectMapper 
>>> interface.
>>>
>>> *Here the "old" code from gwt-jackson*
>>>
>>> *public static interface AltriMetadatiDTOMapper extends 
>>> com.github.nmorel.gwtjackson.client.ObjectMapper>>
>>>  
>>> {} *
>>>
>>> * ... *
>>>
>>> * AltriMetadatiDTOMapper altriMetadatiDTOMapper = 
>>> GWT.create(AltriMetadatiDTOMapper.class); String jsonAltriMetadati = 
>>> altriMetadatiDTOMapper.write(object); *
>>>
>>> *Here the "new" code from domino-jackson*
>>> *@org.dominokit.jackson.annotation.JSONMapper public interface 
>>> AltriMetadatiDTOMapper extends 
>>> org.dominokit.jackson.ObjectMapper>> {}*
>>>
>>> * ... *
>>>
>>> * AltriMetadatiDTOMapper altriMetadatiDTOMapper = 
>>> GWT.create(AltriMetadatiDTOMappe.class); String jsonAltriMetadati = 
>>> altriMetadatiDTOMapper.write(object); *
>>>
>>> but it give to me this error
>>> [ERROR] Errors in 'xxx.java' [INFO] [ERROR] Line 662: Rebind result 
>>> 'xxx.AltriMetadatiDTOMapper' must be a class
>>>
>>> Did anyone know what i'm doing wrong ?
>>>
>>

-- 
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/bd148277-b238-46d0-8448-8d3c5f4009bbn%40googlegroups.com.

Re: gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

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.

Re: gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

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: gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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: Dominokit tools release update

['Frank Hossfeld' via GWT Users]

Awesome work! ...

Vegegoku schrieb am Dienstag, 30. Januar 2024 um 13:08:52 UTC+1:

> We are glad to announce the new releases of Dominokit tools :
>
> *Domino-ui 2.0.0*
> Find release notes here 
> https://github.com/DominoKit/domino-ui/releases/tag/2.0.0
>
> *Domino-history 1.0.3*
> Find release notes here 
> https://github.com/DominoKit/domino-history/releases/tag/1.0.3
>
> *Domino-rest 2.0.0-RC1*
> Moved to jakarta namespace, find release notes here 
> https://github.com/DominoKit/domino-rest/releases/tag/2.0.0-RC1
>
> We would like to remind you that you can now check our documentation for 
> different DominoKit tools within our website :
>
> *The documentation will be updated soon to include and match the new 
> changes.*
>
> - *Domino-ui documentation*
> https://dominokit.com/solutions/domino-ui/v2/docs/getting-started
>
> - *Domino-jackson documentation*
> https://dominokit.com/solutions/domino-jackson/v1/docs/getting-started
>
> - *Domino-rest documentation*
> https://dominokit.com/solutions/domino-rest/v1/docs/getting-started
>
> - *Domino-history documentation*
> https://dominokit.com/solutions/domino-history/v1/docs/getting-started
>
> Your feedback is welcome and please help us spread the knowledge
>

-- 
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/4d23fa9d-5ec0-4d46-950f-d7c55a59a632n%40googlegroups.com.

Re: gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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 ...

['Frank Hossfeld' via GWT Users]

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.

Re: gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

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: The GWT application hangs on the loading screen

['Frank Hossfeld' via GWT Users]

Did you check in the Developer Tools ->. Network if the nochache.js gets 
loaded?

Antonio Capone schrieb am Montag, 15. Januar 2024 um 09:53:58 UTC+1:

> Hello everyone and thanks for the advice you are giving me.
> The nocache.js file is regularly generated and loaded. I don't think I 
> have a problem with the URI because I can also see the home page grid but 
> nothing more. No errors appear in the developer tool. Note that I upgraded 
> from GWT 2.1 to GWT 2.7 and before that I had no problems.
> Can you give me some other suggestions?
> Thanks again.
>
> Il giorno domenica 14 gennaio 2024 alle 05:39:07 UTC+1 Craig Mitchell ha 
> scritto:
>
>> I use a servlet filter to tell the browser not to cache the nocache files:
>>
>> public class ServletFilter implements Filter {
>>   private static final String NO_CACHE = ".nocache.js";
>>
>>   @Override
>>   public void doFilter(ServletRequest request, ServletResponse response, 
>> FilterChain 
>> chain) throws IOException, ServletException {
>> String requestURI = ((HttpServletRequest)request).getRequestURI();
>>
>> // Don't cache the nocache
>> if (requestURI.endsWith(NO_CACHE)) {
>>   setNoCache((HttpServletResponse)response);
>> }
>> chain.doFilter(request, response);
>>   }
>>
>>   private void setNoCache(HttpServletResponse httpResponse) {
>> Date now = new Date();
>> httpResponse.setDateHeader("Date", now.getTime());
>> httpResponse.setDateHeader("Expires", now.getTime() - 8640L);
>> httpResponse.setHeader("Pragma", "no-cache");
>> httpResponse.setHeader("cache-control", "public, max-age=0, 
>> must-revalidate");
>>   }
>> }
>>
>> On Saturday 13 January 2024 at 2:54:08 am UTC+11 Jeff Hill wrote:
>>
>>> There may have been some Chrome updates in the last few months; 
>>> occasionally, I must hard refresh to get the latest code from nocache.js.  
>>> (That did not happen in  years past)
>>>
>>> Anyway, I always check in Developer Tools in Chrome to make sure there 
>>> are no errors in the "Console" and all the necessary files are being loaded 
>>> in the "Network" tab.
>>> On Thursday, January 11, 2024 at 6:42:14 AM UTC-7 Frank Hossfeld wrote:
>>>
>>>> Check if the nochache.js gets loaded at a applicaiton staert or if it 
>>>> got a 404. In this case something with the URI is not ok.
>>>>
>>>> Antonio Capone schrieb am Donnerstag, 11. Januar 2024 um 10:56:55 UTC+1:
>>>>
>>>>> Hi all. I deployed an app using GWT on Cloud. It's deployed and 
>>>>> working, but when you log in, the browser window just says "Loading" and 
>>>>> seems to hang indefinitely. Works fine locally in Eclipse.
>>>>> Has this ever happened to you? Is there anyone who can help me 
>>>>> understand why this happens?
>>>>> Many 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/21799f50-40b7-4360-9865-ff1796d48a75n%40googlegroups.com.

Re: The GWT application hangs on the loading screen

['Frank Hossfeld' via GWT Users]

Check if the nochache.js gets loaded at a applicaiton staert or if it got a 
404. In this case something with the URI is not ok.

Antonio Capone schrieb am Donnerstag, 11. Januar 2024 um 10:56:55 UTC+1:

> Hi all. I deployed an app using GWT on Cloud. It's deployed and working, 
> but when you log in, the browser window just says "Loading" and seems to 
> hang indefinitely. Works fine locally in Eclipse.
> Has this ever happened to you? Is there anyone who can help me understand 
> why this happens?
> Many 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/561f301d-8bd9-4a99-8b10-93c2cf2cc3d3n%40googlegroups.com.

Re: Is moving away from RPC a good idea?

['Frank Hossfeld' via GWT Users]

Using domino-rest, the POJO have usually only one annotation: @JSONMapper.

Vassilis Virvilis schrieb am Donnerstag, 11. Januar 2024 um 09:35:05 UTC+1:

> First of all thanks for doing this work. It is hugely appreciated and 
> required in order to avoid GWT and GWT projects look like zombies in a dead 
> landscape.
>
> I am using RestyGWT and yes I also believe it uses Generators 
> (GWT.create() ?). I am facing a problem there since RestyGWT is deadish 
> itself.
>
> One of the reasons I abandoned GWT-RPC was Jsinterop. With Jsinterop you 
> can include and link to js libraries in the client. Some of them require 
> data from the backend e.g. datatables.net, d3 etc. GWT-RPC is not 
> compatible with them so I would need to use RequestFactory, which I never 
> liked or another framework. So why have two of them? Use one. Go to JSON. 
> RestyGWT was the only viable choice at the time.
>
> With Resty-GWT I can have my POjOs *without annotations*, and I can share 
> them between backend, frontend and other clients (non web). RestyGWT has 2 
> backends:
> - an older private jackson like (forked) implementation. That's the one I 
> use.
> - a newer gwt-jackson based one. This one never worked for me.
>
> Furthermore I have invested in RestGWT and I have some custom patches so 
> RestyGWT can transmit my generics.
>
> At this point domino-jackson and domino-rest looks like the way forward 
> but from a quick look require annotations in the POJO and this is something 
> that I would like to avoid.
>
> Just my 2 bits. Sorry if incoherent...
>
>
>
>
> On Wed, Jan 10, 2024 at 9:45 PM Michael Conrad  wrote:
>
>> You should investigate the DominoKit project. They have a much more 
>> up-to-date JSON/Jackson-ish implementation.
>>
>> Ref: https://github.com/DominoKit/domino-rest
>>
>>
>>
>> On 1/10/24 11:26, Christian Hebert wrote:
>>
>> Hi guys, I've seen the changes in the new release regarding jakarta 
>> servlets, which is great, it's a step toward jakarta but to this day,  GWT 
>> is still based on the Servlet API 3.1. 
>>
>> Prior of seeing that change, I tried to move away from RPC calls and use 
>> http requests instead. I found a nice library called RestyGWT (
>> https://resty-gwt.github.io/) who can really simplify the process of 
>> handling json data from/to a Rest API.
>>
>> So I converted my GWT remote servlets to a Rest API, made a few minor 
>> changes in my client code and voilà, I was able to deploy it on a Jakarta 
>> Application server since there is no GWT involved on the server side 
>> anymore. 
>>
>> The last version of RestyGWT has been release in 2020 so I'm not sure how 
>> active this project is but from what I've seen it's enough for me.
>>
>> So, I would like to get your thoughts on that.  Would you go on that 
>> road? stick to RPC calls and wait for a version of GWT based on Jakarta? 
>> build your "own" GWT with the changes introduced in the vew version?
>> -- 
>> 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/8fa7dc19-2a15-442d-93b2-adebb947046cn%40googlegroups.com
>>  
>> 
>> .
>>
>>
>> -- 
>> 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/156e77ff-25bd-4743-8798-0d0347d1866d%40newsrx.com
>>  
>> 
>> .
>>
>
>
> -- 
> Vassilis Virvilis
>

-- 
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/1f442a59-8e19-427e-84c1-9a3914cfe08bn%40googlegroups.com.

Re: DominoKit has a new home

['Frank Hossfeld' via GWT Users]

Great work!

Mamta Bansal schrieb am Freitag, 3. November 2023 um 14:25:48 UTC+1:

> Congratulations to the whole team, great work 
>
> On Fri, Nov 3, 2023, 09:06 Andrea Stocchero  wrote:
>
>> well done guys!
>>
>> Il giorno mercoledì 1 novembre 2023 alle 18:31:31 UTC+1 
>> lofid...@gmail.com ha scritto:
>>
>>> Great work! Congrats!
>>>
>>> Vegegoku schrieb am Dienstag, 31. Oktober 2023 um 09:41:19 UTC+1:
>>>
 Exciting news — https://dominokit.com is live! Our new platform stands 
 as a beacon of inclusion, unifying detailed documentation in one 
 centralized location to empower and educate. We invite you to explore this 
 collective reservoir of knowledge, designed to support and inspire. Please 
 help us spread the word by sharing this resource with your network and 
 beyond. Together, we can create a vast community of shared wisdom and 
 resources.

>>> -- 
>> 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/74c23d48-1d9b-47f9-b77d-d4e313ba9a96n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/8bcd4fd7-64b3-46f4-bdb8-ebe499c9b59bn%40googlegroups.com.

Re: gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

The plugin uses the same input (except for the artifactId) as Thomas 
Broyer's gwt-maven-archetype. 

> One small error, the top level pom.xml has 3 blank lines between every 
XML line.  Just like this:  
https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/clean-modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/pom.xml
  
Easy to fix up, so only a very minor error.

Yeah, that is something annoying. But, no chance to fix it. It seams, it is 
a bug inside the maven 
archetype: https://issues.apache.org/jira/browse/ARCHETYPE-584. Think, we 
have to wait until this one gets fixed.

Craig Mitchell schrieb am Samstag, 6. Januar 2024 um 02:13:46 UTC+1:

Thank you!  I was struggling to get Springboot to work with GWT, and this 
did it beautifully!

One thing I messed up:

> Define value for property 'package' teamdrift: : jar

I thought it meant how did I want to package the output, as I need an 
executable jar, not a war.  But it meant what did I want my Java package to 
be.  lol.

One small error, the top level pom.xml has 3 blank lines between every XML 
line.  Just like this:  
https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/clean-modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/pom.xml
  
Easy to fix up, so only a very minor error.

Thank you for making this awesome tool!

On Tuesday 2 January 2024 at 8:46:30 pm UTC+11 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/7ec2d4c3-22b1-4e70-98ea-fcff81e14042n%40googlegroups.com.

Re: Strategies for dealing with large number of languages?

['Frank Hossfeld' via GWT Users]

The strings of our application are located on the server. At applicaiton 
start, the client loads the constants from the server and load it into a 
factory. The factory has a method that accepts a key and return the value. 

benefits: 
- no new permutations
- change language without reloading the application
- adding a language is just adding an new property file on the server

drawback:
- a little bit longer start up time
- no support from the IDE
Ralph Fiergolla schrieb am Donnerstag, 4. Januar 2024 um 09:55:26 UTC+1:

> Hi! 
> Since a big part of our string content comes from database records anyway, 
> we decided to go without any static texts but use dynamic labels. Initial 
> concerns about performance and memory footprint have proven to be 
> unfounded. That is, despite working in the context of European Institutions 
> we go with a single static language and avoid the compile time performance 
> bottleneck of having a large number of permutations. 
> Cheers,
> Ralph 
>
> On Thursday, January 4, 2024 at 1:29:08 AM UTC+1 Alexander Bertram wrote:
>
>> Hi there,
>> We have been using GWT to build our product for a very long time. 
>> Recently, we've faced a new challenge as we've steadily been increasing the 
>> number of supported translations of the application to support a global 
>> audience. We're up to 24 languages, and could conceivably hit 40 in the 
>> coming year.
>>
>> With all of these languages, come more permutations! We've stripped away 
>> browser-specific permutations, but we do have a mobile version of the app, 
>> which means that we have 2 x 24 permutations = 48.
>>
>> So far, we've addressed this problem by increasing the size of the VM 
>> that builds the app, but even with 16 vCPUs it takes 10-12 minutes to build 
>> the app. I'm experimenting with increasing to 32 vCPUs, but so far I can't 
>> get the build time to drop linearly.
>>
>> Anyone else out there using alternate strategies? Is it worth trying to 
>> create some sort of distributed cache from the intermediate files the 
>> compiler writes out? Load translations dynamically at runtime instead? Or 
>> just through more hardware at it :-)
>>
>> Just curious to hear what others are doing?
>>
>> Best,
>> Alex
>>
>

-- 
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/2498f396-b504-4d3a-8e15-63936ef37b64n%40googlegroups.com.

gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

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/07f24747-de6f-4a68-a619-120168cf2053n%40googlegroups.com.

Re: Seeking Guidance: GWT Version with Resolved XSS Vulnerabilities - Which One to Use?

['Frank Hossfeld' via GWT Users]

you should never deploy your tests into production.
flosanlop17 schrieb am Donnerstag, 21. Dezember 2023 um 17:52:49 UTC+1:

> I am currently working on some security incidents reported in an 
> application that uses GWT, in its version 2.5.0 according to the report for 
> this version there are security vulnerabilities related to XSS, I was 
> reading a little the real notes of the versions above this one for example 
> 2.5.1 indicates that this vulnerability was fixed,  But on investigation it 
> seems that this is not the case, according to the attached references this 
> novelty still persists.
>
> Continue reading the actual notes of later versions, but it's not clear if 
> any security patches were worked on in new versions.
>
> Reading the forum, I notice that in version 2.8.1 a vulnerability related 
> to XSS was also identified again.
>
> My question is which version then I could use that currently has these 
> vulnerabilities fixed.
>
> Very thanks for your help.
>
> References
> https://www.openwall.com/lists/oss-security/2013/08/05/3
> https://www.openwall.com/lists/oss-security/2013/08/05/1
> https://groups.google.com/g/google-web-toolkit/c/Tx29wSZ8SZQ
>

-- 
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/690aec4c-81d8-4e0e-946d-58979cddc5c3n%40googlegroups.com.

Add news page to gwtproject.org - proposal

['Frank Hossfeld' via GWT Users]

Hi,
I think we all meet people, who are telling us, that GWT is dead. We all 
know, that this isn't true. You just have to look into the GitHub repos or 
this room. It is very vital. For devs & decision makers, who are not so 
familiar with this room or who do not check the GWT repos, and they only 
take a look at the gwtproject side ... there is no information about 
upcoming release or features or the activity inside the community. 

So I created this proposal to add a news page to gwtproject.org.

The idea is, to have one place where the community can anouce things 
related to GWT, J2CL or related third party libs.

To do so, I added a new entry on the left called news and created this news 
page (the table of content is visible, cause it runs locally (I hope ... 
:-))). To add news, someone has to create an issue (gwt-site repo - we 
should create a template for that) and maintainers will add the news.

Also, in another step, I would like to update the "who is using GWT" site 
with much newer projects. But this will be another PR.

Please add your comments here: 
https://github.com/gwtproject/gwt-site/pull/348

-- 
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/ac5afd2b-3f24-444f-be00-34e0bd09d7a5n%40googlegroups.com.

Re: user.agent problem with GWT 2.1.0 and GXT 4.1

['Frank Hossfeld' via GWT Users]

I think so, as long as you are not using any language features of Java > 8

Victor Colina schrieb am Freitag, 8. Dezember 2023 um 14:55:58 UTC+1:

> Thanks for the response, If I change to GWT 2.9 I can still use jdk 17? Or 
> I have to go lower?
>
> On Friday, December 8, 2023 at 9:05:37 AM UTC-4 Frank Hossfeld wrote:
>
>> Assuming you are using GWT 2.10.0, GXT expects a few things, (f.e.: 
>> user-agent ie8) which have been removed in GWT 2.10.0.
>> You have to stay with GWT 2.9.0. (see: 
>> https://docs.sencha.com/gxt/4.x/guides/announcements/Announcements.html)
>>
>> Victor Colina schrieb am Donnerstag, 7. Dezember 2023 um 17:48:29 UTC+1:
>>
>>> I'm trying to compile a simple GWT project with GXT 4. The compilation 
>>> works unitl I add the gxt.
>>>
>>> [image: imagen_2023-12-07_124453814.png]
>>>
>>>
>>>
>>> This is my gwt.xml file.
>>>
>>> [image: imagen_2023-12-07_124712961.png]
>>>
>>> If anybody can help me, 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/18521e2f-f9a8-4b23-acfb-e9fa42ea556fn%40googlegroups.com.

Re: user.agent problem with GWT 2.1.0 and GXT 4.1

['Frank Hossfeld' via GWT Users]

Assuming you are using GWT 2.10.0, GXT expects a few things, (f.e.: 
user-agent ie8) which have been removed in GWT 2.10.0.
You have to stay with GWT 2.9.0. 
(see: https://docs.sencha.com/gxt/4.x/guides/announcements/Announcements.html)

Victor Colina schrieb am Donnerstag, 7. Dezember 2023 um 17:48:29 UTC+1:

> I'm trying to compile a simple GWT project with GXT 4. The compilation 
> works unitl I add the gxt.
>
> [image: imagen_2023-12-07_124453814.png]
>
>
>
> This is my gwt.xml file.
>
> [image: imagen_2023-12-07_124712961.png]
>
> If anybody can help me, 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/a70c7e58-5f46-4269-92cc-82c0e4e2b914n%40googlegroups.com.

Re: Project moved now compile errors

['Frank Hossfeld' via GWT Users]

Might be a problem with the jdk version ... 
IIRC, record was added in Java 14 (not sure). It looks like a jdk version > 
13 is used to build. 
Not sure if SmartGWT is supporting newer jdk version than version 8.

Next problem might be Eclipse itself. Newer Eclipse version need something 
greater than Java 8.

Hope that helps. 
 

blackh...@gmail.com schrieb am Mittwoch, 13. September 2023 um 08:58:57 
UTC+2:

> Hi,
>
> We have a so called build server, where we build all our projects. This is 
> just a server where eclipse is running and where we build our projects with 
> ant.
>
> As the server was/is getting old (windows 2008R2), we have set up a new 
> one (windows 2022). We installed eclipse with the same configuration as on 
> the old server. Same Java versions installed too.
> We checked out the projects and now 1 of the projects does not compile the 
> web stuff.
> The other projects do build normal.
>
> I have attached the compile log. Can anyone explain what is happening and 
> what i am missing to fix this?
>
> Regards,
>
> Jasper
>

-- 
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/84dc4c24-7ce9-471e-803c-92db836e4982n%40googlegroups.com.

Nanu v2.12.1 released

['Frank Hossfeld' via GWT Users]

We found some bugs and fixed them ... 

https://github.com/NaluKit/nalu/releases/tag/v2.12.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/2ddd8c89-3fa8-4d04-92d3-49d3b65e0095n%40googlegroups.com.

Nalu v2.12.0 released

['Frank Hossfeld' via GWT Users]

This release adds new method.
For more information see: 
https://github.com/NaluKit/nalu/wiki/14.-Controllers-&-Composites#unbind-method-since-v2120

-- 
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/5b07aaef-6c44-444a-9a84-961323350f30n%40googlegroups.com.

Re: Can one convince code server to ignore an error and continue?

['Frank Hossfeld' via GWT Users]

IIRC you need to update a few classes of GXT to get it running with GWT 
2.9.0+. And GWT 2.10.0 dropped the support for ie8, ie9 & ie10 which will 
also cause problems. 

Jens schrieb am Mittwoch, 15. Februar 2023 um 13:21:38 UTC+1:

> I am currently stuck with an error in a commercial GWT widget library that 
> our project uses (GXT v4.0.2). The code generated by that library contains 
> a bug: it contains a GWT.create(…)-call where the argument is an 
> interface and not a class.
>
> Actually GWT.create() usually takes an interface and during GWT 
> compilation that interface is either replaced by a class using GWT rebind 
> rules stored in any *.gwt.xml file or a GWT generator will be executed 
> (also defined in *.gwt.xml file) which generates a class that implements 
> that interface. Maybe you can find that rebind rule in any *.gwt.xml file 
> provided by GXT and then you might see why it fails to replace that 
> interface with a concrete class. You should be able to add your own custom 
> rebind rules then to fix the issue.
>
> But when I try to execute the application in development mode on a local 
> Tomcat then the compilation that is triggered in code server by the first 
> UI request yields this:
> CodeServer has option -[no]failOnError. Have you tried that?
>
> But I could imagine that this kind of error will still be reported because 
> GWT wants to replace GWT.create() with new SomeClass() but does not know 
> how to do it. If -nofailOnError does not work you have to try fixing the 
> root cause of the issue as described above.
>
> -- J.
>

-- 
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/8122fa52-e1b4-42e8-b7db-02660b657183n%40googlegroups.com.

Re: Is there some description anywhere how to set up a decently usable GWT 2.10 development environment?

['Frank Hossfeld' via GWT Users]

Depending on your backend (Spring Boot or not) you can generate ready to go 
Maven-projects. Use Maven goals to start the code server and the server. 
And debug inside the browser. No need for a GWT-plugin inside the IDE. 

Use: https://github.com/tbroyer/gwt-maven-archetypes to generate a module 
with separate client, server and shared module in case you do not have a 
Spring Boot server. Use: 
https://github.com/NaluKit/gwt-maven-springboot-archetype in case you 
prefer to use Spring Boot. This one also generates separate client-, 
shared- and server-module. Both are perfect starts for an update. 

When working on Windows use: *mvn:devmode *instead of *mvn:codeserver* .

Frank schrieb am Donnerstag, 15. Dezember 2022 um 14:34:52 UTC+1:

> Maybe https://dev.to/ibaca/modern-gwt-first-steps-509k can help
>
> As a note. We use the paid version of IntelliJ. This has a GWT plugin 
> aboard which we find very usefull.
>
> Op woensdag 14 december 2022 om 20:50:58 UTC+1 schreef 
> maple.c...@gmail.com:
>
>> It is a bit of a challenge to get GWT to work well in IntelliJ with 
>> Jetty. We finally got it working very well a year ago, thanks to a site 
>> that explained some of the key points for getting it to work. The URL of 
>> the site is 
>> https://imsavva.com/how-to-debug-gwt-in-2021-and-fix-error-scanning-entry/
>>
>> The site is a bit dated, but the main points are still valid. If you use 
>> jetty, do use jetty 10, not jetty 11. GWT 2.10.0 works. Java versions all 
>> the way to java 17 work. Not sure whether jetty 9.4 works with Java 9 and 
>> up; we never tried that combination. Over the last year, our combinations, 
>> with IntelliJ, have been:
>>
>> 1. gwt 2.8.2 with builtin jetty 9.2 (initially, before we moved to using 
>> the jetty plugin in IntelliJ))
>> 2. gwt 2.8.2, gwt 2.9.0, and gwt 2.10.0 with jetty plugin (jetty 9.4) and 
>> java 8
>> 3. gwt 2.10 with jetty 10 and jetty plugin and java 17. This is what we 
>> have now. The GWT configuration is a tiny bit different as GWT 2.10.0 can 
>> only handle Java 11 right now, not Java 17.
>>
>> We never found the need to use the jetty plugin until we needed to use 
>> WebSocket and jetty 9.2 can't handle WebSocket very well. There was a way 
>> to get around it, but unfortunately that way was blocked by Java 9 and up. 
>> A year ago, I found out about that site. I followed the instructions from 
>> that site and got everything working with some changes, as my source code 
>> structure is different from his.
>>
>> Let me know if you encountered an issue you can't solve. I don't check 
>> the mailbox of this email address, so posting the questions here is better. 
>> If this is the right way to go about this in this group.
>>
>> We have been using GWT since the beginning, for almost 15 years now. We 
>> started using jetty about 8 years ago; before that, we were using Tomcat 
>> (and Apache). We migrated from Eclipse to IntelliJ about 3 years ago. We 
>> never use maven as we need to be able to build the whole system with 
>> everything included in a repo (except Java). Just a weird requirement, that 
>> is for sure. So, we are still using ant to build our war file as well.
>>
>> On Wednesday, December 14, 2022 at 12:53:35 PM UTC-5 nam...@gmail.com 
>> wrote:
>>
>>> Hi,
>>>
>>> We succesfully use the gwt 2.10 dev mode to run and debug our 
>>> applications. We had to overide the JettyLauncher class to be able to run 
>>> it with java > 8.
>>> What kind of issue do you have with the dev mode (with gwt plugin on 
>>> eclipse) ?
>>>
>>> Le mer. 14 déc. 2022 à 18:22, mmo  a écrit :
>>>
 Over the last years our GWT development environment has eroded more and 
 more.
 First the browser plugins seized to work, then the 
 mapping/JS-code-backtranslation stopped working and recently also the IDE 
 plugins for Eclipse and IntelliJ that would deploy the generated artifacts 
 to the correct places, start the code server and allowed some minimalistic 
 form of debugging seized to work. It is getting more and more not just 
 frustrating but really horrible and "mission impossible".

 Thus a while ago I began an effort to port our application to GWT 2.10 
 and Java 8 (our "production version" still runs with GWT 2.7 and Java 7 
 and 
 I can't go to higher Java versions due to some libraries, yet). 

 Meanwhile I found my way through all the library conflicts so that I am 
 able to build and generate a version that runs fine when deploying the 
 generated .war file to to a Tomcat Server (v8.5 in our case).

 But being able to building a running version is one thing. The other is 
 to have a development setup that doesn't shy away developers crying and 
 yelling but allows to do decent client side code debugging.

 With the "old" GWT plugin the commands "gwt:run" and "gwt:debug" didn't 
 work anymore with GWT 2.10. I keep getting the following error during 
 Jetty 
 

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

['Frank Hossfeld' via GWT Contributors]

Same here. It's time to move forward. Java 8 and IE 11 should be dropped. 
In case someone will stay with Java 8 he can use GWT 2.10.0.
I'll expect new versions of GWT will - in many cases - bring new language 
features. So, someone staying with Java 8 is not interested in updating. 
 

stockiNail schrieb am Sonntag, 7. August 2022 um 18:10:35 UTC+2:

> In my opinion, my 2 cents, the support of JAVA 8 and IE11 should be 
> dropped because very close to be obsoleted.
> Whoever is using these platforms could stay on current version of GWT 
> where they are supported.
> I still have some applications based on Java 8 but they will remain with 
> GWT 2.8.2 and when I could migrate them, I'll go to Java 11 or more and GWT 
> accordingly.
>
> Il giorno sabato 6 agosto 2022 alle 22:38:52 UTC+2 m.conr...@gmail.com ha 
> scritto:
>
>> My company is also migrating everything to JDK 17. The less opportunity 
>> for bitrot in future versions, the better.
>>
>> On Sat, Aug 6, 2022 at 11:06 AM Manfred Tremmel  
>> wrote:
>>
>>> In my company Java 8 was dropped long ago, at the moment the migration 
>>> from 
>>> Java 11 to 17 is in progress. So from my side, let's cut off the old 
>>> stuff.
>>>
>>>
>>> -- 
>>> 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-co...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/7868638.WIiY39HZoD%40t470
>>> .
>>>
>>

-- 
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/83423468-8742-4dfe-b296-f8c5c7a713a8n%40googlegroups.com.

Re: [WARN] 404 - GET //10.14.0.224:8888/sampleapp/sampleapp.nocache.js

['Frank Hossfeld' via GWT Users]

Inside your module descriptor, is the rename-to attribute of the module tag 
also "sampleapp"?

abhiy...@gmail.com schrieb am Montag, 18. Juli 2022 um 19:18:00 UTC+2:

> Hello Everyone,
>
> I am getting below error when trying to start application through GWT 
> plugin in eclipse. I am using GWT 2.9.0. I have renamed my module to 
> *sampleapp 
> *and in the html file I have used the below script in html file
> * *
>
> 07:18 20:56:17 |  INFO | [main] | 
> org.eclipse.jetty.server.handler.ContextHandler:doStart(824) | Started 
> c.g.g.d.s.j.WebAppContextWithReload@238d3e2d{}
> 07:18 20:56:18 |  INFO | [main] | 
> org.eclipse.jetty.server.AbstractConnector:doStart(330) | Started 
> ServerConnector@6e4484d6{HTTP/1.1,[http/1.1]}{0.0.0.0:}
> 07:18 20:56:18 |  INFO | [main] | 
> org.eclipse.jetty.server.Server:doStart(399) | Started @32366ms
> *[WARN] 404 - GET //10.14.0.224:/ * 
> *sampleapp**/**sampleapp**.nocache.js (10.14.0.224)*
>Request headers
>   Host: 10.14.0.224:
>   Connection: keep-alive
>   User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) 
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36
>   Accept: */*
>   Referer: http://10.14.0.224:/sampleapp.html
>   Accept-Encoding: gzip, deflate
>   Accept-Language: en-US,en;q=0.9
>Response headers
>   Cache-Control: must-revalidate,no-cache,no-store
>   Content-Type: text/html;charset=iso-8859-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/5af94871-9887-4280-9429-717c3ac7f5a6n%40googlegroups.com.

Re: Compatibility of GWT 2.10.0 with GXT 2.3.1.a

['Frank Hossfeld' via GWT Users]

GWT packages have still the same name. AFAIK, there are no changes on 
package names.
In case you start using GWT modules, you will have to use the packages 
starting with 'org.gwtproject'. 

Starting with GWT 2.10.0 you can 'com.google.gwt' or 'org.gwtproject' as 
groupId inside the Maven dependency. Starting with one of the next release 
of GWT, only the 'org.gwtproject' groupId can be used.  

leon.p...@gmail.com schrieb am Montag, 18. Juli 2022 um 15:33:09 UTC+2:

> From what I gathered, packages have been renamed from **.google.** to 
> **gwtproject** or smth.
> So without a gxt update to cover for the new packages, I doubt you can 
> upgrade your project.
>
> There is one simple way to check, just update the GWT version in your 
> dependency manager (maven or whatever you use) and you'll find out soon 
> enough.
>  
> Op maandag 18 juli 2022 om 06:56:23 UTC+2 schreef priyako...@gmail.com:
>
>> Hello Team,
>>
>> we use following jars in our application - 
>> GXT .jar -2.3.1.a
>> GWTx.jar -   1.5.3
>> Log4j-gwt.jar - 1.0
>>
>> Wanted to know that will recent update of GWT 2.10.0 compatible with 
>> above dependencies.
>>
>>

-- 
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/7c2e3720-6129-441f-906d-d3e2f3f5d21dn%40googlegroups.com.

Nalu 2.10.1 is available ...

['Frank Hossfeld' via GWT Users]

We found bugs and fixed them … a new Nalu version (2.10.1) is available!

For more information, see: 
https://github.com/NaluKit/nalu/releases/tag/v2.10.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/570c4e28-d3bb-4469-b49f-62f696dan%40googlegroups.com.

Re: What will happen to GWT development in the future?

['Frank Hossfeld' via GWT Users]

I think, you should ask this questions inside the GWT Gitter room 
. 

> GWT moves away from Google and focuses on J2CL etc.
Yes and gave the responsibility to the community. This is not unusual. See 
Angular, JSF, etc. 
First, don't worry about the future of GWT. There will be releases and 
future development for GWT 2. And the community is working hard to make the 
transition from GWT to J2CL as easy as possible. New frameworks and the GWT 
modules will work with J2CL and GWT. 
 

-- 
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/5e5eaa3d-45dc-44c2-9a2b-c6eaefd31d6cn%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

['Frank Hossfeld' via GWT Users]

You can use domino-rest without using maven. But Maven will make things 
much easier.

There are several examples demontrating the use of the Domino-Stack 
(including domino-rest) Also, in most cases, it does not depend on Eclipse. 
F.e.: 
check: 
https://github.com/NaluKit/nalu-examples/tree/main/nalu-complex-app-example. 
This example demonstrate how to do things in Nalu. This example uses 
domino-rest for the communication. (I am pretty sure Ahmad & Rafat have 
similar examples using the domino stack). Just follow the instructions 
inside the readme.txt. All you need to do is to install Java and Maven and 
make it available from your terminal. 


hprc schrieb am Dienstag, 24. Mai 2022 um 02:15:12 UTC+2:

> Re [domino-rest]
> It's a great API, you can use POJO and REST respectively.
> However, I don't know how to use ECLIPSE + GWT + MOVEN, so it's sad that I 
> can't use it right away.
>

-- 
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/af91eff0-b471-4c17-96bb-e73fc7a4c07bn%40googlegroups.com.

Nalu 2.10.0 released

['Frank Hossfeld' via GWT Users]

This week we released Nalu 2.10.0 (see: https://github.com/NaluKit/nalu).

There is a new feature added, that improves the way how to add an event 
handler to the event bus. All you need to do is to add the '@EventHandler' 
to the method. 
For more informations, see: 
https://github.com/NaluKit/nalu/wiki/08.-Eventbus#event-handling

And we just add a new complex Nalu example, that uses a lot of the 
features, Nalu provides. And it might give you an impression how to do 
things in Nalu. (see: 
https://github.com/NaluKit/nalu-examples/tree/main/nalu-complex-app-example)

Enjoy.

-- 
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/dbe51838-cec8-4489-8019-9e5db2a0fa65n%40googlegroups.com.

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

['Frank Hossfeld' via GWT Contributors]

No problems with this version. works as expected. 
Great work! 

juan_pablo_gardella schrieb am Dienstag, 26. April 2022 um 13:50:12 UTC+2:

> After removing an old plexus-utils as suggested at #152 
> , I was able to 
> compile and run the application without issues so far. Great work!
>
> On Mon, Apr 25, 2022 at 2:25 PM Freddy Boucher  
> wrote:
>
>> 2.10.0-new-groupid-3 works like a charm (in addition of 
>> net.ltgt.gwt.maven/gwt-maven-plugin 1.0.1)
>> Thanks
>>
>> Le dimanche 24 avril 2022 à 21:34:23 UTC+2, juan_pablo_gardella a écrit :
>>
>>> Tried with Maven 3.8.5 and still fails with same issue. Reported at 
>>> https://github.com/tbroyer/gwt-maven-plugin/issues/152
>>>
>>> On Sun, Apr 24, 2022 at 3:59 PM Colin Alworth  wrote:
>>>
 I've pushed a new build with version 2.10.0-new-groupid-3 that has 
 several @SuppressWarnings("deprecation")s added, and hopefully will solve 
 the WARN logging issue.

 -- 

>>> 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-co...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/28cff012-2206-48a8-8882-11b0ea945046n%40googlegroups.com
  
 
 .

>>> -- 
>> 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-co...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/051780f4-fa98-45c2-ad36-1ebb40a38f7an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/5dee4e9f-ee9d-4d92-a567-24903e01abd0n%40googlegroups.com.

Re: URGENT: GWT build crash with out of memory

['Frank Hossfeld' via GWT Users]

First, you should fix this:

*ompiling module project2.**Project2*


*   Validating units:  Ignored 12 units with compilation errors in 
first pass.Compile with -strict or with -logLevel set to TRACE or DEBUG to 
see all errors.*


*set the logLevel to TRACE and check the error message. That should point 
you to your problems. *

vie...@gmail.com schrieb am Mittwoch, 2. März 2022 um 14:34:55 UTC+1:

> Hi there,
>
> you can check, if there are the correct values with jconsole or visualvm. 
> Please check the java call you are using to build the project. Maybe you 
> can add there a general -Xmx4000M (or something).
>
> Best regards
>
> viny...@gmail.com schrieb am Dienstag, 1. März 2022 um 16:27:41 UTC+1:
>
>> Hi,
>>
>> We are having a quite big project, every thing was going in control but 
>> from last few days our GWT project is crashing while building WAR (with 
>> error out of memory).
>> "*Compiling module project2.**Project2*
>>
>>
>>
>>
>> *   Validating units:  Ignored 12 units with compilation errors in 
>> first pass.Compile with -strict or with -logLevel set to TRACE or DEBUG to 
>> see all errors.   Compiling 1 permutation*
>> *  Compiling permutation 0...*
>>
>> *[ERROR] OutOfMemoryError: Increase heap size or lower 
>> gwt.jjs.maxThreadsjava.lang.OutOfMemoryError: Java heap space*"
>>
>> *System  (PC) configuration on which we are building WAR is:*
>> OS = WINDOWS SERVER 2019
>> PROCESSOR = XEON (R) CPU E3-1225 V5 @ 3.3Ghz
>> CORE = 4
>> RAM = 64GB
>> HARD DISK = HDD 
>> C (OS drive) =  203GB free of 243GB
>> E (drive) =  501GB free of 642GB
>> F (drive) =  467GB free of 976GB
>>
>> *rest please find the PC images attached.*
>>
>>
>> *GWT build configuration is:* 
>> gwt.module=project1.Project1 project2.Project2
>> gwt.output.dir=/org.yournamehere.Main
>> gwt.compiler.output.style=OBFUSCATED
>> gwt.compiler.jvmargs=-Xmx61440m
>> gwt.compiler.local.workers=1
>> gwt.compiler.logLevel=INFO
>> gwt.shell.output.style=OBFUSCATED
>> gwt.shell.logLevel=TRACE
>>
>> gwt.shell.jvmargs=-Xmx61440m
>> gwt.shell.java=
>> gwt.version=2.6
>> gwt.shell.code.server.port=9997
>> gwt.shell.port=
>>
>> *rest please find the  gwt.properties file attached.*
>>
>>
>> *WAR file info:*
>>
>> *.WAR (Size on disk) = 577MB
>>
>> *project1.Project1*
>> *.gwt.rpc  (count) =  1
>> *.gwt.rpc (size) =  8kb
>> *.cache.html (size) = 335kb
>> *.nocache.js = 6kb
>>
>> *project2.Project2*
>> *.gwt.rpc  (count) =  876
>> *.gwt.rpc (size) =  9.76MB
>> *.gwt.rpc (max) = 19kb - 11kb (158 files), 10kb - 8kb (718 files)
>> *.cache.html (size) = 1713kb
>> *.nocache.js = 6kb
>> deferredjs\4D7A0074D70FA749A45BC16CDEAAFFE3\*.cache.js (count) = 856
>> deferredjs\4D7A0074D70FA749A45BC16CDEAAFFE3\*.cache.js (size) = 28.6MB
>> deferredjs\4D7A0074D70FA749A45BC16CDEAAFFE3\*.cache.js (max) = 4043kb(1 
>> file), 446kb - 101kb (38 files), 98kb - 1kb (817 files). 
>>
>>
>>
>> *WE REQUEST TO ALL PLEASE HELP! AS DELIVERY OF THE WAR IS REQUIRED ON 
>> URGENT BASIS.*
>>
>>
>>
>>
>>
>>

-- 
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/779bee4d-1e31-4f55-81b0-bac2f4b063fbn%40googlegroups.com.

Re: Performance Comparison GWT Transpiler with MacBook Pro M1 Pro processor

['Frank Hossfeld' via GWT Users]

No, sorry ... closed source. Yep, I agree with. Don't think, that the 
graphics CPUs will have an impact of the compile time.
So, the M1 Pro is a great choice for developers. Now I am waiting for the 
next Mac Pro ...

Jens schrieb am Montag, 6. Dezember 2021 um 10:32:15 UTC+1:

> I did some tests with one of my larger GWT projects. It takes 3:55 on my 
>> "old" MacBook Pro 16" i9 2.4 GHz, 64 GB RAM. Same project build on a new 
>> MacBook Pro M1 Max 64 GB takes roundabout 2:00. That's an incredible 
>> improvement. 
>
>
> Is that project public? Then I would try it with my M1 Pro 32gb which is 
> IMHO the best value for developers, unless you do graphics stuff.
>
> -- J. 
>

-- 
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/c3bacc36-a959-4833-be07-6304e3f5705cn%40googlegroups.com.

Nalu v2.6.0 is released

['Frank Hossfeld' via GWT Users]

A new Nalu version is released. 2.6.0 for GWT 2.9.0 
(https://github.com/NaluKit/nalu/releases/tag/v2.6.0) and version 
2.6.0-gwt-2.8.2 
(https://github.com/NaluKit/nalu/releases/tag/v2.6.0-gwt-2.8.2). Besides a 
few bug fixes there is a new feature added: constraints for parameter 
inside a route. Here you find more informations: 
https://github.com/NaluKit/nalu/wiki/14.-Controllers-&-Composites#parameters

-- 
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/10d41daa-080b-4635-916c-fb5298c0ae4dn%40googlegroups.com.

Re: Trying to get GWT app deployed in local Tomcat (using Eclipse)

['Frank Hossfeld' via GWT Users]

For example: if you are using Maven, you can switch to Thomas Broyer's GWT 
Maven Plugin and create a Multi module project with separate modules for 
shared, client & server. This configuration will work with newer Java 
version (> 8) without any problems. Personally I have switch to Spring Boot 
on the server side.  server starts not more than 20s. 
mmo schrieb am Freitag, 6. August 2021 um 17:05:55 UTC+2:

> I am (trying to) upgrade our GWT-based legacy application to use newer 
> Hibernate, Spring and other library versions. After some (substantial) 
> pull-ups this works mostly fine by now when deploying a fully generated and 
> packaged .war file, but building this thing always takes forever and day 
> (the infamous permutations and other steps...).
>
> Since the Jetty that's built into the GWT plugin has issues with newer 
> (multi-release) .jar files (see my different discussion) I had to switch 
> deployment of the application to Tomcat (which is our target server anyway) 
> also for development. 
>
> To speed up the development cycle I am thus trying to get this thing also 
> to run as unpacked file using Eclipse's Tomcat "server bridge". This plugin 
> deploys a web application to a temporary directory in the eclipse workspace 
> and then starts Tomcat passing it the proper settings using VM options 
> like: 
> -Dcatalina.base="\.metadata\.plugins\org.eclipse.wst.server.core\tmp0"
>  
> -Dcatalina.home="C:\Program Files\Apache Software Foundation\Tomcat 8.5" 
> -Dwtp.deploy="\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps"
> .
>
> With that the application begins to start up, I get to the point where I 
> login and get the initial index.html page but as soon as some GWT-generated 
> Java-script has to be loaded things stall. As I had to learn the entire GWT 
> generated code which - as I found out - gets compiled into directories 
> named like C
> :\Users\\AppData\Local\Temp\gwt-codeserver-8682038074388630768.tmp\.WebWar\compile-1\war\
>  is 
> *not* copied over or linked into the wtpwebapps directory.
>
> I experimented a bit and if one creates a Junction (a kind of soft-link in 
> Windows) in the wtpwebapps\   directory pointing to that 
> generated GWT code then  the application indeed starts loading the UI. 
> However, at some point it invariably dies with a popup that it couldn't 
> load the application from Super Dev Mode Server at http://localhost:9876. 
> So there are (at least) two things missing: the GWT code has to be hooked 
> or copied into the generated server configuration and apparently there must 
> also be a Dev Server available. At this point - since I don't understand 
> this (Super) Dev Mode well enough - I decided to ask in this forum:
>
> Has anyone got this working so that one can deploy a GWT application to a 
> local Tomcat instance without first having to pack everything up and deploy 
> as a .war file, so that one can essentially continue to run and debug as 
> one used to using Jetty before using the maven goals gwt:run or gwt:debug? 
>
> Is that described or documented anywhere? Or would some kind soul mind to 
> share his/her knowledge on how to get this working? 
> It doesn't have to be for Eclipse - IntelliJ would be ok as well. The 
> point is that it should not require the lengthy build-package-deploy cycle 
> because a cycle-time of >10 minutes is just unbearable for development. 
>
> Any suggestions welcome!
>

-- 
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/4c59cd47-16c4-4bbe-8542-432b7927b14en%40googlegroups.com.

New version of iban4g

[Frank Hossfeld]

The latest version of iban4g adds Egypt to the IBAN registry:

https://github.com/NaluKit/iban4g/releases/tag/v2.0.3

-- 
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/52320237-4d62-40c3-b9c6-7508f9e973abn%40googlegroups.com.

New release of iban4g

[Frank Hossfeld]

The latest version of iban4g adds Egypt to hte IBAN registry:

https://github.com/NaluKit/iban4g/releases/tag/v2.0.3

-- 
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/c9bdb87b-53bf-4044-b7fa-08d6a8bcc49dn%40googlegroups.com.

Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

['Frank Hossfeld' via GWT Contributors]

@eliasbalasis: Why you need 5 steps to run the application in a GWT multi 
module project? I have two runnning configuration, one for the code server 
another for the server. I, personally, prefer Spring boot. Starts very 
fast! And, if you running your app in the cloud, Spring Boot is awesome.


t.br...@gmail.com schrieb am Dienstag, 13. April 2021 um 20:04:04 UTC+2:

> Which features are you talking about? Which would you lose by switching to 
> using a *real* Jetty server alongside GWT CodeServer?
>
> Le mar. 13 avr. 2021 à 20:01, Richi Plana  a écrit :
>
>> As a user and non-contributor, I would vote for bumping up versions (Java 
>> 7 to 8, Jetty to 9.4). The move to Java 8 is something I would have to do 
>> if I had any Java 7 projects left. And Jetty has lots of used features that 
>> I'm not hearing proposals for replacement for.
>> On 2021-04-11 9:15 a.m., Jens wrote:
>>
>> Hi, 
>>
>> we all know the issue: DevMode bundles Jetty and people are using it even 
>> though we do not recommend it. Consequently people are complaining that 
>> bundled Jetty is too old. So every once in a while we upgrade it.
>>
>> Currently with GWT 2.9.0 the situation is:
>> - GWT SDK is compiled to Java 7 byte code
>> - GWT Compiler requires ASM 7.x to support Java 11
>> - DevMode bundles Jetty 9.2 which uses ASM 5.x
>> - gwt-dev.jar can only bundle a single Jetty, since we do not relocate 
>> it. However there is already a question asking for Jakarta Servlet support, 
>> e.g. Jetty 11 / Tomcat 10.
>>
>> Currently the ASM version misalignment between Jetty 9.2 and GWT compiler 
>> causes classpath issues. This could be fixed by upgrading to Jetty 9.4 and 
>> consequently compiling GWT SDK to Java 8 byte code as that is a requirement 
>> for Jetty 9.4.
>>
>> However given the new Jakarta namespace and first questions about 
>> supporting it, I am wondering if it wouldn't be wiser to remove embedded 
>> Jetty from DevMode now, invest some work to make GWT-RPC and RequestFactory 
>> useable with old javax.servlet and new jakarta.servlet namespaces and 
>> finally cut a 2.10 or 3.0 release given the removal of embedded Jetty.
>>
>> Personally I would strongly vote for removal because GWT nowadays is in 
>> maintenance mode with only very few changes here and there to support J2CL 
>> better. Even reviews from contributors are rare these days I guess. Every 
>> action we take nowadays should take maintenance effort into account and a 
>> low maintenance effort is obviously preferred. If we upgrade Jetty to 9.4 
>> we still have that Jakarta issue coming up more often in the future for 
>> sure.
>>
>> Generally this would be a decision made by GWT steering group but I have 
>> no idea if this group still exists. So I am asking here for a decision how 
>> to move on.
>>
>> -- J.
>> -- 
>> 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-co...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/622544a8-85d5-41c5-b8da-7a733667eb89n%40googlegroups.com
>>  
>> 
>> .
>>
>> -- 
>> 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-co...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/c317be1c-55d9-f255-0b0f-e05da19240ee%40gmail.com
>>  
>> 
>> .
>>
>

-- 
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/2fb3b18a-506e-4c24-b59c-bd279aa62e12n%40googlegroups.com.

[gwt-contrib] Re: Asking for decision on DevMode embedded Jetty support

['Frank Hossfeld' via GWT Contributors]

I agree with Jens. I would - also - vote for the removal. 

Besides the things Jens mentioned, we have Thomas Broyer's 
gwt-maven-archetype (for Jetty/Tomcat) or the 
gwt-maven-springboot-archetype (for Spring Boot) to generate Maven multi 
module projects. So, it is quite easy to generate a multi module project. 
And it is well documented and maintained.

 I would prefer spending some times on updating gwtproject.org (the part of 
how to start) instead of udpating the Jetty stuff.

I know, that there are many single module projects outside that run with 
devmode. I moved sereval of them to a new project structure inn the last 
years. In many cases this is not really hard to do. 

 


Jens schrieb am Sonntag, 11. April 2021 um 23:04:13 UTC+2:

> For reference:
>
> Jetty ASM issues:
> https://github.com/gwtproject/gwt/issues/9606
> https://github.com/gwtproject/gwt/issues/9693
> https://github.com/gwtproject/gwt/issues/9720
>
> Jakarta servlet support question:
> https://github.com/gwtproject/gwt/issues/9727
>
> Other embedded Jetty related issues:
> jrt: URLs not recognised with Java 9+: 
> https://github.com/gwtproject/gwt/issues/9582
> Class loader leak protection code causes (ignorable, yet annoying) error 
> logs in Java 9+: https://github.com/gwtproject/gwt/issues/9561
>
>
>
>
>

-- 
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/35490456-4697-47bf-8537-7c46609bc346n%40googlegroups.com.

Re: Elemental2-compatible Activities (and Places)?

[Frank Hossfeld]

Sorry, wrong link. This one is correct: 
https://gitter.im/gwtproject/gwt-modules

Frank Hossfeld schrieb am Sonntag, 7. März 2021 um 12:47:27 UTC+1:

> Gordan Krešić schrieb am Samstag, 6. März 2021 um 18:24:17 UTC+1
>
>> I can see it still references widgets, so definitely not a final port, 
>> but 
>> if you are interested I can propose pull request based on my own port 
>> which 
>> uses elemental2.dom.HTMLElement instead of widgets. However, that should 
>> be 
>> up to a debate, because I believe more modular approach would be needed 
>> to 
>> cover most use cases: widgets, elemental2's HTMLElement, elemento's 
>> IsElement and possibly others.
>>
>
> Yeap, that's the problem. (and the reason, why Nalu uses several plugins, 
> to deal with the different implementations). We haven start the discussion 
> yet. And ATM, I am not sure, if IsWidget and Widget, is already migrated.I 
> think not. Think it is gwt-widgets, which is not yet done too, or at least 
> it is still in progress. Maybe something to discuss inside the gwt-modules 
> room: https://github.com/gwtproject
>

-- 
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/0c7e4ac9-d739-48f4-9ef2-b0ea252dfcedn%40googlegroups.com.

Re: Elemental2-compatible Activities (and Places)?

[Frank Hossfeld]

Gordan Krešić schrieb am Samstag, 6. März 2021 um 18:24:17 UTC+1

> I can see it still references widgets, so definitely not a final port, but 
> if you are interested I can propose pull request based on my own port 
> which 
> uses elemental2.dom.HTMLElement instead of widgets. However, that should 
> be 
> up to a debate, because I believe more modular approach would be needed to 
> cover most use cases: widgets, elemental2's HTMLElement, elemento's 
> IsElement and possibly others.
>

Yeap, that's the problem. (and the reason, why Nalu uses several plugins, 
to deal with the different implementations). We haven start the discussion 
yet. And ATM, I am not sure, if IsWidget and Widget, is already migrated.I 
think not. Think it is gwt-widgets, which is not yet done too, or at least 
it is still in progress. Maybe something to discuss inside the gwt-modules 
room: https://github.com/gwtproject

-- 
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/7456d7ab-a8fa-4765-ac05-109a45ce8137n%40googlegroups.com.

Re: Elemental2-compatible Activities (and Places)?

[Frank Hossfeld]

There are a few places where are the progress of the module update is 
tracked:


https://docs.google.com/spreadsheets/d/1b1D9fEqRh5lZ8cqMJtYoc_25rfTRvsuJkTtS2vjgi3o/edit#gid=0
https://docs.google.com/spreadsheets/d/15WXfiklnTeqjRLI8gKj5iyGk7iDhnuQHGcpYJgpNlmQ/edit#gid=0
https://github.com/FrankHossfeld/gwt-modules (still in progress)

And yes, the Activities module is not migrated yet.

If you are looking for J2CL/Elemental2 ready frameworks, take a look here:

   - dominokit/domino-mvp 
   - nalukit/nalu   (Disclaimer: I am the 
   author)
   

Gordan Krešić schrieb am Donnerstag, 18. Februar 2021 um 20:23:17 UTC+1:

> Is there a port of com.google.gwt.activity.* classes that work with 
> elemental2 (HTML)Elements instead of widgets?
>
> I can find only port of Places (https://github.com/gwtproject/gwt-places), 
>
> but no activities.
>
> I can't find that sheet with progress on porting GWT components to 
> J2CL/GWT3 
> - what is the status of Activities and Places on that regard?
>
> -gkresic.
>
>

-- 
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/f56a79b5-98f0-4584-977a-16d4024ee8d8n%40googlegroups.com.

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

[Frank Hossfeld]

A few years ago, a client of mine was thinking about switchung to Vue. So, 
I startet learning Vue. To do so, I search the internet, bought a book, 
install npm, code the examples and so on ... 

Two or three weeks later, my virus scanner (oh yes, I am a Mac user that 
has a virus scannner ... my client requested it) found two trajans which 
were trying to transfer Bitcoins, loaded via npm initiated by my Vue 
development. 

After some research I get to know, that this is a common issue, when using 
npm. Bad Boys trying to conquer a repo, add bad code, deploy it and 
distribute the files via npm. 

I think, you need to get some attention on which file you load. Or, better 
have a clean room where all the js files are located (after an audit ...)

Not sure, if this is a common issue or just due to my carelessly ... but it 
makes my scare.  

pavel@gmail.com schrieb am Sonntag, 24. Januar 2021 um 12:36:40 UTC+1:

> Hi, I see that everyone leaves 2c, so I will do the same.
> But before few words about my background - 6 years with GWT+SmartGWT and 
> now 3 years with VueJS + Vuetify + Typescript.
>
> Definitely, it's much faster to prototype an application using VueJS.
> To manage the state(Vuex) and routes(vue-router) is simple and does not 
> matter what UI components you are going to use.
>
> But, in the long-term development, I see that maven is better than npm - 
> simpler to set up a multimodule project with some common settings and 
> dependencies.
> In JS world npm does not support modules. Yarn workspaces help a bit but 
> it works just for private projects(no way to deploy it to the remote 
> repository).
> Typescript helps to write a code but in 99% of cases, 3rd libraries 
> contain only d.ts files without Javadoc. So, you need to open a website 
> with documentation because it's not clear what the library does.
> Refactoring - forget. Event idea can't properly resolve usages of your 
> methods.
> After webpack to understand where has the error happened it's like a 
> mission impossible. 
> Testing - better to write functional code because to mock classes is not 
> so easy as with mockito or easymock.
> With JS/TS you write code slower because IDE does not resolve or properly 
> resolve what to import, especially if code comes from another module.
>
> So, in long term, I guess GWT provides better and simple development and 
> support.
>
> середа, 23 грудня 2020 р. о 09:16:49 UTC+1 vas...@gmail.com пише:
>
>> Hm the thread was about why not using java for frontend development but 
>> now has general tips for GWT.
>>
>> The padlet is cool. Thanks for assembling it.
>>
>> My 2c.
>>
>> I have used GWT RPC in the past but I was not happy with it. The main 
>> reason was that I couldn't decouple server and client from GWT 
>> dependencies. The closest you could make was with an intermediate project 
>> that hosted the interface files.
>>
>> The issue was solved for me with RestyGWT in the client and Apache 
>> CXF/Rest in the server. Totally separate and the only files I share are my 
>> POJO files.
>>
>> Sharing POJO definitions between client and server is the biggest 
>> advantage of GWT for me along with static typing in the frontend. Can't 
>> live without these two.
>>
>> Maybe there is a way to automatically create or define POJOs that is 
>> language independent so I could completely decouple frontend from backend. 
>> I haven't found such a way that is not completely dynamic and which throws 
>> the IDE search and usage features out of the window.
>>
>> Hope that helps.
>>
>>   Vassilis
>>
>>
>>
>>
>> On Tue, Dec 22, 2020 at 7:27 PM lofid...@gmail.com  
>> wrote:
>>
>>> Some tips I could say:
>>>
>>>- GWT is a transpiler / compiler to JavaScript, *so the result only 
>>>runs on Web browser, no server component*. Server container or Web 
>>>server only used for delivering the HTML, JS and CSS. So actually you 
>>> could 
>>>just use the result JS from the file system and make a double click on 
>>> the 
>>>HTML file to open your web app (JS).
>>>- The simplest example I build is the Java Calculator from this 
>>>article: http://bit.ly/WebJavaStory. In this simple Maven example 
>>>you can see how to run the web app, how to code, transpile and unit test 
>>>and also to debug the simple calculator all with web browser.
>>>
>>> I'm using GWT since 2006 / 2007 and until today I haven't seen any 
>>> comparable tools which makes your work very productive, especially as a 
>>> Java developer.
>>>
>>> Hope this helps! Have fun!
>>>
>>> lofid...@gmail.com schrieb am Dienstag, 22. Dezember 2020 um 12:40:39 
>>> UTC+1:
>>>
 We also have a Padlet for GWT 

 I try to collect all the information about GWT / J2CL on one Black 
 Board: https://padlet.com/lofidewanto/gwtintro

 There are articles, presentations, groups and other information for a 
 modern GWT / J2CL development...

 Hope this helps!

 mysare...@gmail.com 

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

[Frank Hossfeld]

Lofi has some interesting things to look at:  
* GWT Awesome Library List (Gwit a LiLi)
* there is also a boot starter for gwt, but I do not recall the name.

Good starting points are:
*  gwt-maven-archetypes: https://github.com/tbroyer/gwt-maven-archetypes
*  https://github.com/NaluKit/gwt-maven-springboot-archetype if you prefer 
Spring Boot on the server 
side: https://github.com/NaluKit/gwt-maven-springboot-archetype
* There is also are archetype creator from DominoKit
* Nalu project 
generator: http://www.mvp4g.org/boot-starter-nalu/BootStarterNalu.html 
(Disclaimer I am the author)

And a good place to ask your questions: https://gitter.im/gwtproject/gwt

Hope that helps.

mysare...@gmail.com schrieb am Freitag, 18. Dezember 2020 um 02:01:24 UTC+1:

> I am new here, so hello everyone.
> I am very interested in this topic. I have gotten tired of the whole 
> javascript ecosystem. I did not know that you could easily have GWT run 
> only on the frontend and used jee/spring/whatever on the backend as you 
> please. I always thought it was a client-server bundle.
> Is there a tutorial that shows how it can be done?
> How is the compilation speed for code-change/webpage-refresh? I have done 
> scala many years, so I understand how frustrating it can be, even though 
> scala is amazing.
> Thanks
> On Sunday, October 18, 2020 at 11:15:42 PM UTC+2 peter.j...@gmail.com 
> wrote:
>
>> On Mon, Oct 19, 2020 at 1:56 AM lofid...@gmail.com  
>> wrote:
>>
>>> Thanks Craig for the info...
>>>
>>> I'm not familiar with React (only Hello World )
>>>
>>> Can you integrate React with these GWT React frameworks? So write your 
>>> components in Java and integrate them back into React JavaScript?
>>>
>>>- https://github.com/GWTReact/gwt-react
>>>- https://github.com/react4j/react4j.github.io
>>>
>>> I don't know whether it is possible?
>>>
>>
>> It may be possible in react4j to publish a java component as a react 
>> component but not without significant overhead/boilerplate. It is also 
>> possible to consume a js react component from within react4j with a little 
>> overhead and we built some of our early apps like this. However, react4j's 
>> sweet spot is when the majority of the application is written in java.
>>
>> With gwt-react it is much easier to both consume js components and 
>> publish java components ... except for the normal constraints of publishing 
>> java to js. My guess is that the sweet spot for gwt-react is for 
>> applications that combine js components into a java app but I have never 
>> used it in anger.
>>
>>
>> -- 
>> Cheers,
>>
>> Peter Donald
>>
>

-- 
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/c3fe1f27-becf-4933-83a5-b48a65a89d0en%40googlegroups.com.

iban4g - v2.0.0

[Frank Hossfeld]

Hi all,

just released iban4g 2.0.0. (https://github.com/NaluKit/iban4g)

iban4g is a port of Artur Mkrtchyan's iban4j project - a library for 
generation and validation of the International Bank Account Numbers IBAN 
(ISO_13616) and Business Identifier Codes BIC (ISO_9362) - so that it will 
work with Java, GWT and/or J2CL. 

This release contains several PRs and bug fixes that - at the moment -  are 
not released in the original lib.

-- 
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/60b14345-8e36-4130-8147-117c6466b8c1n%40googlegroups.com.

Re: Share Header, Footer, ... in different views with UIBinder

[Frank Hossfeld]

There is a project generator, that generates a Nalu project. The generated 
project has a header, footer, navigation and content area.The content area 
will change when clicking a navigation item. It works in the same way as 
the way, Thomas mentioned, but is based on Nalu instead of Activities and 
Places. Nalu is a routing based framework to create applications. It uses 
the same patterns but in a different implementation. May be it helps to 
learn it. 

http://www.mvp4g.org/boot-starter-nalu/BootStarterNalu.html

ATM there is a bug inside the generator, if you select Domino-UI. Domino-UI 
updates a method name and I did not update the generator. (will do it 
during as soon as I have some free time)
You need to replace 'setLeftAddon' with 'addLeftAddOn'.


tonio@gmail.com schrieb am Donnerstag, 8. Oktober 2020 um 18:49:10 
UTC+2:

> Thanks a lot Thomas,
>
> II have already read the pages you propose, but maybe I have some gaps 
> because I really don't understand the system.  A concrete example with the 
> code would surely help me. Is there an example of how to do this? I guess 
> it already exists but I can't find it after several hours of searching. 
> Thank you very much for your help
> Le jeudi 8 octobre 2020 à 16:35:06 UTC+2, t.br...@gmail.com a écrit :
>
>> If *all* your "views" share the same header/footer/nav, then they should 
>> be part of your "shell", with your ActivityManager only managing the "main" 
>> part of the screen.
>> See https://blog.ltgt.net/gwt-21-activities/ and 
>> https://blog.ltgt.net/gwt-21-activities-nesting-yagni/ (wow, 10 years 
>> old!)
>>
>>
>> On Thursday, October 8, 2020 at 2:39:50 PM UTC+2, Guillen Antonio wrote:
>>>
>>> Hi all,
>>>
>>> I am still learning GWT and now I want to build views using 
>>> materialdesign  (with MVP and activity/places)  sharing the same header, 
>>> footer and side navigation. I don't found examples or tutorial to do this 
>>> and I have no idea how to do.
>>>
>>> Thanks for your help
>>>
>>> Antonio
>>>
>>

-- 
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/a269c740-1524-4793-96ee-a2d81803271cn%40googlegroups.com.

Re: Eclipse Version

[Frank Hossfeld]

Hi,

please use: http://www.mvp4g.org/boot-starter-nalu/BootStarterNalu.html to 
generate a maven project. (you need to replace 'setLeftAddon' with 
'addLeftAddOn' to fix a Domino-UI change).

follow the instractions of the readme.txt. 

-- 
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/1a7342c0-6d23-4266-83ca-eba91617d5eeo%40googlegroups.com.

Re: Is there any way to use GWT 2.9 with Java 11 using Eclipse GWT plugin?

[Frank Hossfeld]

Use this to generate a multi module artifact:

https://github.com/tbroyer/gwt-maven-archetypes 


shahra...@gmail.com schrieb am Freitag, 7. August 2020 um 18:23:52 UTC+2:

> is there any documentation for how to set it up, we are not maven 
> oriented. I appreciate a link or document...
>
> On Thu, Aug 6, 2020 at 2:57 PM lofid...@gmail.com  
> wrote:
>
>> GWT Eclipse plugin is not maintained anymore... So to use the newest one 
>> you could move to pure Maven or Gradle... I only use Maven sofar and it 
>> works well...
>>
>> shahra...@gmail.com schrieb am Dienstag, 28. Juli 2020 um 00:11:58 UTC+2:
>>
>>> We have a huge GWT project (GWT 2.7, JDK 1.7, Eclipse) everything works 
>>> perfect. We are planning to upgrade to Java 11 and GWT 2.9 which has been 
>>> recently released. However Java 1.7 is retiring and getting obsolete we 
>>> have to move on and upgrade. Since last week we are trying to create a 
>>> development environment like the existing one but there is no success. I 
>>> was wondering whether anyone out there is struggling with the same issue, 
>>> any hint, solution or hacking the eclipse plugin would be greatly 
>>> appreciated.
>>>
>>> Eclipse plugin comes with GWT (2.7 and 2.8.1)
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "GWT Users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-web-toolkit/l_E1Y8XKg7k/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, 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/c9461274-510c-4661-8a73-28ad39fc35ecn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/4e288466-9bde-4c99-bc12-3adc311c58aen%40googlegroups.com.

Re: [gwt-contrib] Re: Resolving cycle dependency between gwt-safehtml & gwt-safecss

['Frank Hossfeld' via GWT Contributors]

>
> Personally I would go with 'org.gwtproject.gwt-safecss' as groupid. It 
>> will make it much easier for gwt users to work with the module.
>>
>> What do you think?
>>
>
> Do you really mean org.gwtproject.gwt-safecss as groupId‽ I.e. 
> org.gwtproject.gwt-safecss:gwt-safecss coordinates‽
>

Oh, sorry. I mean org.gwtproject.safecss. you are right.
 

> I'd be OK with org.gwtproject:gwt-safecss, but how about 
> org.gwtproject.safetypes grouping both gwt-safehtml and gwt-safecss? (and 
> possibly gwt-safeuri, gwt-safehtml-templates 
> gwt-safehtml-templates-processor if we split further)
> Or org.gwtproject.safe-html-types, inspired by 
> https://github.com/google/safe-html-types 
> 
> ?
>

I like the idea, renaming the repo to gwt-safe-html-types and using as 
group id 'org.gwtproject.safe.type.html', 'org.gwtproject.safe.type.css', 
'org.gwtproject.safe.type.uri' ... sounds good to me.  
 

> Or just keep using the "root" package name as the groupId: 
> org.gwtproject.safehtml:gwt-safehtml (and then annotation processor, etc.) 
> and org.gwtproject.safecss:gwt-safecss (and later possibly 
> org.gwtproject.safeuri:gwt-safeuri)
>

At the first look, I would go with  'org.gwtproject.safe.type.*'. 

 

-- 
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/f44ee683-daad-4bc9-9098-c486438638bbo%40googlegroups.com.

Re: [gwt-contrib] Re: Resolving cycle dependency between gwt-safehtml & gwt-safecss

['Frank Hossfeld' via GWT Contributors]

Thanks everybody for input. 

As @Colin already mentioned I was talking about option 4 of Thomas list. I 
have moved gwt-safecss as separate modules into gwt-safehtml. (Need to add 
a note at the existing GitHub repo of gwt-safecss that the modules have 
moved after the PR is merged). I made a PR: 
https://github.com/Vertispan/gwt-safehtml/pull/6. Everybody is welcome to 
discuss the PR. 

There is one thing that needs to be discussed:
Atm the name of the module is the last part of the groupid. For example 
gwt-editor: 'org.gwtproject.editor'. So, we have an easy rule how the 
groupid and artifatid is created. 

Moving gwt-safecss into gwt-safehtml, we will have the first time two 
modules in one repo. Both modules share the same parent Maven module.  If 
we do nothing, the rule mentioned above will work for gwt-safehtml but not 
for gwt-safecss. gwt-safecss has the groupid 'org.gwtproject.safehtml' 
cause of the parent pom. I changed that, so that the groupid of gwt-safecss 
is 'org.gwtproject.safecss'. But doing this is very unusual for a Maven 
multi module project.

Personally I would go with 'org.gwtproject.gwt-safecss' as groupid. It will 
make it much easier for gwt users to work with the module.

What do you think?  

 

-- 
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/fea3fafb-9c7a-4d30-8cc8-aca898cd5c53o%40googlegroups.com.

[gwt-contrib] Resolving cycle dependency between gwt-safehtml & gwt-safecss

['Frank Hossfeld' via GWT Contributors]

To prepare GWT for j2cl we need to move the modules out of GWT, replace 
generators with ATP, etc. This is in progress and the first modules 
(SNAPSHOT) are released.

Migrating gwt-safehtml and gwt-safecss runs into a problem, cause 
gwt-safehtml depends on gwt-safecss and gwt-safecss depends on 
gwt-safehtml. This is a serious issue, cause one can not be build and 
tested without the other. 

To solve this issue, we are looking for solutions.

One solution might be to move the tests out of gwt-safehtml. But then 
gwt-safehtml needs to be build and deployed before the tests run and might 
be deployed with failing tests. That looks like a bad solution.  At the 
moment the idea is to move the sources and tests from gwt-safecss into 
gwt-safehtml and delete gwt-safecss. This will remove the cycle dependency 
between these two modules, but doing so, the module will be the first 
module that contains two old modules in one new.

Any other ideas how to solve this issue?

-- 
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/a8d6c785-c8d9-4eba-8cc2-0b42ecac1124o%40googlegroups.com.

Re: Elemental2 and widgets

[Frank Hossfeld]

Please take a look here: https://gitter.im/hal/elemento for more 
information and here: https://github.com/hal/elemento/issues/82

-- 
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/0e46ed5d-409a-41a7-a19e-61e4b751ec98o%40googlegroups.com.

[gwt-contrib] Re: Thurs Jun 18 2020 GWT Contributors call

['Frank Hossfeld' via GWT Contributors]

We plan to record at least the session about frameworks, but will not do it 
this time, because we have not decided how to. 

The next part is, when recording we record questions from participants. Not 
sure, If we need then a legal agreement. 

-- 
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/521c0779-ce55-4e8c-8c0f-0ab0e884b3b3o%40googlegroups.com.

[gwt-contrib] Re: Thurs Jun 18 2020 GWT Contributors call

['Frank Hossfeld' via GWT Contributors]

Hi Bernhard,

no, we don't do it this time, but plan it for the future. 
But, I think, there will be more hangouts. So, maybe next time.

Regards,
Frank

-- 
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/cc305839-6395-413d-be59-1e0cc066a303o%40googlegroups.com.

[gwt-contrib] Re: HashCode H$ property should be not enumerable

['Frank Hossfeld' via GWT Contributors]

Remove support for IE8, IE9 & IE10, keep IE11 supported. Think, most of 
business users have updated to IE11 or Edge. 

-- 
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/398a11a8-bbd4-48a5-82fe-5faf0a4af2fco%40googlegroups.com.

Re: how to run gwt newer version in netbeans

[Frank Hossfeld]

You can generate a ready to use Multi Module maven project using TB 
GWT-Maven-Plugin here: 
http://www.mvp4g.org/boot-starter-nalu/BootStarterNalu.html

Once you have generate the project, you can import it as a Maven project 
into your IDE (did not test it with NetBEans, but expect it is working). 
Now, follow the the instructions of the readme.txt and start codeserver and 
jetty.

paste the URL into your browser (chrome) and hit return. 

Once running open the dev tools, move to sources and start debugging.

-- 
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/00a5e899-4854-469e-a321-a56e39a9eb8b%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Frank Hossfeld]

Atm the community is very active. We are working on GWT modules: replacing 
generators and JSNI, testig the migraed moules against J2CL, etc.
Besides that, many new frameworks are evolving.

Take a look at this rooms:
https://gitter.im/gwtproject/gwt
https://gitter.im/vertispan/j2cl
https://gitter.im/DominoKit/domino
to get more infos.

-- 
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/a3ae5c60-6dc7-43f0-b3c9-02a6e6d18bf9%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Frank Hossfeld]

You should ask this question here: https://gitter.im/gwtproject/gwt

-- 
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/27aad5bc-85d3-41b1-a642-f9d5e0985b58%40googlegroups.com.

Nalu v2.0.0 is released!

[Frank Hossfeld]

The next version of Nalu  (v2.0.0) is 
released.  A complete list of changes can be found here: release-notes 
.

Maven Central is updated. Please use the Gitter room 
 in case of questions.

Thanks to anyone who helped!

-- 
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/ac6a9f7d-ca3d-44b1-967c-8bb7edf42752%40googlegroups.com.

Re: porting older app from 2.5.0 to 2.8.2

[Frank Hossfeld]

Not sure, if it will work with GWT 2.8, but I would give it a try:

https://github.com/bedatadriven/gxt

-- 
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/bb07702f-f4c5-4c25-9f4c-61b4a35873a5%40googlegroups.com.

Re: porting older app from 2.5.0 to 2.8.2

[Frank Hossfeld]

Just adding the version matrix link to Ignacio's answer:
https://docs.sencha.com/gxt/4.x/guides/getting_started/Versions.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/6b00c826-4644-4bc5-927c-f1908d82b88d%40googlegroups.com.

Re: GWT Screen

[Frank Hossfeld]

You can generate a working GWT project using the Nalu project generator:

http://www.mvp4g.org/gwt-boot-starter-nalu/GwtBootStarterNalu.html

Import the project into your IDE and take a look at the 
NavigationController/NavigationComponent. 
This should help you to understand how to switch screens inside a GWT 
application. 

(Instead a button the project uses a link ... but that makes no difference)

Hope that helps.

-- 
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/43dc6682-431e-41e6-b868-aecda564f860%40googlegroups.com.

Re: Gwt 2.8.2 compilation error

[Frank Hossfeld]

The compile tells you, that there is no source code for: 
org.apache.commons.beanutils.PropertyUtils

Common problem is:

* you did not inherit the module descriptor for the module containing 
PropertyUtils

Just add the module using inherits in your module descriptor. 

But I am pretty sure, PropertyUtils can not be used on the client side ... 
but maybe I am wrong.

-- 
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/79dca1a8-efc1-4460-9adf-250f735b93c3%40googlegroups.com.

Re: Gwt 2.8.2 compilation error

[Frank Hossfeld]

set logLevel=TRACE and fix the 15 compilation errors

-- 
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/5a11fc5b-1ced-4538-8576-e3804f828241%40googlegroups.com.

Re: Is this project active?

[Frank Hossfeld]

Bob, you are right! At the moment, there is no communication, so GWT might 
look dead. 

The only way to get informations for now  is to visit the Gitter rooms for 
gwtproject https://gitter.im/gwtproject/gwt and j2cl 
https://gitter.im/vertispan/j2cl.  

Many contributors are working on GWT 3 to get it work. 

* create gwt modules that work with j2cl (remove JSNI, replace generators, 
etc)
* Colin and Dimitrii (I think) are working on maven j2cl plugins
* Ahmad has written a really nice widget lib which will be j2cl ready (
https://github.com/DominoKit/domino-ui)

Many others are working on frameworks that will work with j2cl like:

* Elemento 
* autorest
* Nalu 
* mvp4g2
* etc.

and many more (sorry, if I missed something and for sure I will, there are 
a lot more). All these libs need to be tested with j2cl, needs docs, etc. 
This is a lot of work, that the contributors are doing in their rare free 
time.

Once, we got more things working, we will move the migrated modules to 
maven central and do announce them. 

And of course we need to update gwtproject.org. But, this is only 
reasonable once we got things working and know, what to write.

For all of you, who are missing more informations, visit the Gitter rooms. 

-- 
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/8d8e9db0-5af9-4567-b86b-ad905d5a6cca%40googlegroups.com.

Re: Is this project active?

[Frank Hossfeld]

Bob, you are right! At the moment, there is no communication, so GWT might 
look dead. 

The only way to get informations for now  is to visit the Gitter rooms for 
gwtproject https://gitter.im/gwtproject/gwt and j2cl 
https://gitter.im/vertispan/j2cl.  

Many contributors are working on GWT 3 to get it work. 

* create gwt modules that work with j2cl (remove JSNI, replace generators, 
etc)
* Colin and Dimitrii (I think) are working on maven j2cl plugins
* Ahmad has written a really nice widget lib which will be j2cl ready (
https://github.com/DominoKit/domino-ui)

Many others are working on frameworks that will work with j2cl like:

* Elemento 
* autorest
* Nalu 
* mvp4g2
* etc.

and many more (sorry, if I missed something and for sure I will, there are 
a lot more). All these libs need to be tested with j2cl, needs docs, etc. 
This is a lot of work, that the contributors are doing in their rare free 
time.

Once, we got more things working, we will move the migrated modules to 
maven central and do announce them. 

And of course we need to update gwtproject.org. But, this is only 
reasonable once we got things working and now, what to write.

For all of you, who are missing more informations, visit the Gitter rooms 
and offer your help. 



-- 
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/4f83b79e-d040-460a-9659-e1ac1a46a257%40googlegroups.com.

Re: GWT MVP Frameworks

[Frank Hossfeld]

I forget to mention:

Another intresting MVP framework is 

* Nalu: https://github.com/NaluKit/nalu 

and 

* Domino-mvp: https://github.com/DominoKit/domino-mvp

-- 
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/46d6b458-196c-4785-9ba3-b955aa7b1e42%40googlegroups.com.

Re: GWT MVP Frameworks

[Frank Hossfeld]

I forget to mention:

Another intresting MVP framework is Nalu: https://github.com/NaluKit/nalu 

-- 
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/63d2bf9c-44cd-4e7f-97ef-c43d9238569b%40googlegroups.com.

Re: Developers Meetup @DEVK "Showdown GWT vs. VueJS" in Cologne Germany

[Frank Hossfeld]

the session will be in German, I guess.

Am Donnerstag, 9. Mai 2019 15:50:08 UTC+2 schrieb Frank:
>
> In German or English ?
>
> Op woensdag 8 mei 2019 22:07:12 UTC+2 schreef Dr. Lofi Dewanto:
>>
>> Hi All,
>>
>> just for you who is living in *Cologne and area, Germany*, we are 
>> hosting a free meetup: *"GWT vs. VueJS"*
>>
>> Here is the description of the meetup:
>>
>> http://bit.ly/DevkGwtVue
>>
>> Frank Hossfeld will show us everything about GWT.
>>
>> If you are in the near just sign in for free. I'm looking forward to have 
>> hot discussions :-)
>>
>> Thanks,
>> Lofi
>>
>

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/9576af97-a378-4ed1-bd67-72d98a44e180%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Tips on libraries

[Frank Hossfeld]

I forgot to mention: There are project generators for mvp4g2: 
http://www.mvp4g.org/gwt-boot-starter-mvp4g2/GwtBootStarterMvp4g2.html and 
Nalu: https://github.com/nalukit/gwt-boot-starter-nalu. So, you can easily 
get an impression how they work.

Both frameworks work well with Domino-UI.

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Tips on libraries

[Frank Hossfeld]

I forgot to mention: There are project generators for mvp4g2: 
http://www.mvp4g.org/gwt-boot-starter-mvp4g2/GwtBootStarterMvp4g2.html and 
Nalu: https://github.com/nalukit/gwt-boot-starter-nalu.

Both frameworks work well with Domino-UI.

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Tips on libraries

[Frank Hossfeld]

Before I start, I would like to say, that I am a contributor of mvp4g and 
the owner of mvp4g2 and Nalu. All these libs could be a replacement for 
GWTP.

As Thomas already mentioned, I would avoid using libs based on GWT 
generators. So mvp4g will be no choice today. Mvp4g2 and Nalu both use 
annotation processors. Mvp4g2 has been successfully tested with J2CL and 
Nalu will also work with J2Cl cause it has no dependency to GWT. If you 
have already build something on mvp4g, I think mvp4g2 should be your 
choice. Otherwise I would give Nalu a try. Mvp4g2 and Nalu do not provide 
any widgets nor something for the communication with the server. 

To communicate with the server I prefer using REST.

In the past I like GXT very much. Currently, I am unsure about the future 
of GXT. My current choice would be Domino-UI, in case I am looking for a 
widget lib. Domino-UI is also ready to go with J2CL and the support of the 
Domino-UI team is awesome.

You will find more informations about mvp4g2 here: 
https://github.com/mvp4g/mvp4g2, about Nalu here: 
https://github.com/NaluKit/nalu and Domino-UI here: 
https://github.com/DominoKit/domino-ui.

May be also interesting: vue-gwt (https://github.com/VueGWT/vue-gwt) 

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Tips on libraries

[Frank Hossfeld]

Before I'll start, I would like to say, that I am a contributor of mvp4g 
and the owner of mvp4g2 and Nalu. All these libs could be a replacement for 
GWTP.

As Thomas already mentioned, I would avoid using libs based on GWT 
generators. So mvp4g will be no choice today. Mvp4g2 and Nalu both use 
anotation processors. Mvp4g2 has been successfully tested with J2CL and 
Nalu will also work with J2Cl cause it has no dependency to GWT. If you 
have already build something on mvp4g, I think mvp4g2 should be your 
chioce. Otherwise I would give Nalu a try. Mvp4g2 and Nalu do not provide 
any widgets nor somnething for the communication with the server. 

To cummincate with the server I prefer using REST.

In the past I like GXT very much. Currently, I am unsure about the future 
of GXT. My current choice would be Domino-UI, in case I am looking for a 
widget lib. Domino-UI is also ready to go with J2CL and the support of the 
Domino-UI team is awesome.

You will ifnd more inforamtions about mvp4g2 here: 
https://github.com/mvp4g/mvp4g2, about Nalu here: 
https://github.com/NaluKit/nalu and Domino-UI here: 
https://github.com/DominoKit/domino-ui.

May be also intresting: vue-gwt (https://github.com/VueGWT/vue-gwt) 

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Nalu is released!

[Frank Hossfeld]

Hi Pavlo,

yes, you are right. I am the Owner of the Nalu & Mvp4g project.

First, looking at mvp4g, I would say, that mvp4g is an awesome framework. I 
used it successfully in many projects in the past. But today, I would not 
start a new project with mvp4g. Mvp4g (which was origanally created by 
Pierre-Laurent Coirier) uses heavily GWT generators. So, with J2CL going 
public it is not the best voice. 

Let's look at mvp4g2. I have rewritten mvp4g and replaced the GWT 
generators with annotation processors. mvp4g2 is tested with J2CL and will 
be no show stopper switching from GWT 2.x to J2CL / GWT 3! My intention to 
create mvp4g2 is to give the mvp4g users an easy upgrade path for the 
future. As you can see on this page, most of the features of mvp4g has been 
implemented in mvp4g2: 
https://github.com/mvp4g/mvp4g2/wiki/Comparision:-Mvp4g-vs.-Mvp4g2, so it 
might be easy to upgrade. There are only a few changes. (Of course, Nalu 
will work with J2CL, too!)

Last year I had a discussion with Ahmad and Colin, which - in the end - let 
me create Nalu. In my opinion, Nalu is a more modern and web-like framework 
than mvp4g/mvp4g2 is. So, let me compare mvp4g2 with Nalu (the big points):

* history:

In mvp4g2 you have to work with history converters, write them and manage 
everything. In Nalu, cause it uses the url to route, you have nothing to do 
for getting  history done. It works out of the box. (Starting with version 
1.2.0 you can tell Nalu to avoid using a token in the url). Nalu can work 
with url or with a hash. It is just a annotation attribute to switch it. 
So, I would say, Nalu is more web like compared to mvp4g2.

* life cycle:

In mvp4g2, once a presenter view, is created, it will be reused all the 
time (except for the case you mark the presenter with multiple=true, but in 
this case you have to create it). In Nalu, a controller (it is the same 
like a presenter in mvp4g2) has a life cycle: start - activate - mayStop - 
deactivate - stop. If case it is needed, a controller can be cached (which 
will reuse the instance of the controller & component). The life cycle 
thing was one of the points many mvp4g users have missed. Nalu works here 
like many other GWT frameworks!

* confirmation:

This is a big deal! In mvp4g2, the confirmation is asynchron. I tis 
possible to do a server call, before to decide to leave the page. In Nalu 
the mayStop method is synchron! Nalu works here like many other GWT 
frameworks!

* visible components:

In mvp4g2, you have to deal by yourself where to add views. In Nalu, the 
framework will do the replacement of the widgets. All you have to do, is to 
make sure, that a node with the selector id exists. And, with Nalu it is 
quite easy to work with different application layouts, because the shell is 
part of the route. I personally prefer the Nalu way to manage the views.

* logging

During development, Nalu logs a lot on the browser console which makes it 
easier to understand, what the framework does. 

* context

Nalu supports an application wide context (to store application infos) and 
injects it into every filter, handler and controller.


Nalu and also mvp4g2 have both an event bus, provide features like filters, 
handlers (controller/presenter without views) and inject instances of the 
eventbus, the view/component, the context and the router into every 
controller / presenter.

But, in my opinion Nalu does it with less code and a little bit more 
elegant, is more like a web application framework than mvp4g2 and I am 
pretty sure, Nalu will also work on the server side (if there is a plugin). 
If you would ask me, which one I choose, I would go with Nalu.

If you have any questions, feel free to contact me here: 
https://gitter.im/Nalukit42/Lobby


If you want to play around with both frameworks, you can generate 

* mvp4g2 projects here: 
http://www.mvp4g.org/gwt-boot-starter-mvp4g2/GwtBootStarterMvp4g2.html

* Nalu projects here: 
http://www.mvp4g.org/gwt-boot-starter-nalu/GwtBootStarterNalu.html


More informations about mvp4g2 can be found here: 
https://github.com/mvp4g/mvp4g2

More informations about Nalu can be found here: 
https://github.com/NaluKit/nalu


There are many examples projects:

* for mvp4g2: https://github.com/mvp4g/mvp4g2-examples

* and even more for Nalu: https://github.com/nalukit/nalu-examples


Last but not least, I would say, regarding the last month, Nalu is more 
popular than mvp4g2.

Hope that helps!   

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: upgrade GWT project from 2.5 to 2.7

[Frank Hossfeld]

Is there a reason why you do not update to GWT 2.8.2?

And to help you fixing the problems: set the logLevel to TRACE. This will 
show you the failing classes ... 

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Nalu is released!

[Frank Hossfeld]

After finishing the work on the 'plugin'-feature and a lot of testing, Nalu 
v1.0.0 is released and the artifacts are deployed to Maven Central.

Nalu is a framework that helps you to create GWT applications similar to 
GWT Activities & Places - with less code - and offers the following 
features:

* Route based navigation
* Supports HTML links and programmatically routing thanks to a router.
* Full support of the browser's back- forward- and reload-button.
* An optional loader that will be executed at application start to load 
data from the server.
* A client side context, router and event bus which will be automatically 
injected in every controller, filter, loader and handler. (Handler have 
only access to the context and the event bus)
* Filters to intercept routing.
* Separation of views into a controller and a component with framework 
sided instantiation.
* A controller life-cycle using `start`-, `mayStop`- and `stop`- similar to 
GWT Activities.
* Controller based handler manager, that will remove all handlers from the 
event bus in case the controller is stopped to prevent memory leaks 
(handler registrations must be added to the manager).
* Support for UiBinder (nalu-plugin-gwt)
* Nalu composites to support smaller units
* Controller & component caching
* Component creation inside a controller to support GWT replacement rules 
and static factory methods
* Multi Shell Support
* works with nearly every widget lib (tested with: GWT, GXT, Domino-UI, 
Elemento, Elemental2, GWT-Meterial) 
* Supports Maven multi module projects to separate an application in 
smaller parts (plugin feature)

More informations about Nalu can be found here:

https://github.com/NaluKit/nalu

There are already several examples available that shows the implementation 
of Nalu's features and how to create an application using Nalu:

https://github.com/nalukit/nalu-examples

To start playing around, you can use the Nalu Project generator located 
here:

http://www.mvp4g.org/gwt-boot-starter-nalu/GwtBootStarterNalu.html

(The project generator is based on Nalu and uses Domino-UI (
https://github.com/DominoKit/domino-ui) Thanks @vegegoku for creating the 
UI)

To get in touch with the developers, use the Nalu Gitter room: 
https://gitter.im/Nalukit42/Lobby  

Last but not least, I would like to thank everybody who helped getting Nalu 
done.

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: First I heard of "Domino UI"

[Frank Hossfeld]

I did some coding with Domino-UI for some examples (testing my framework). 
It is awesome. Looks nice and offers a lot of widgets. For my next project 
it would  be my first choice. The folks from Domino UI make a good job. 
Support is great and I get always help.

But keep in mind, Domnino UI is still in progress. So, there might be some 
chances before the final release.

I read some things about vue-gwt, but did not use it. So, I am not able to 
tell you, which one is better. 

Am Montag, 17. September 2018 16:26:45 UTC+2 schrieb Michael Joyner:
>
> First I heard of "Domino UI".
>
> Any one out there with experience with it?
>
> regarding UI there is now good libs for GWT if you are looking for 
> material design: for example
> Domino-ui 
>  
> : type safe UI libs based on elemental2 and elemento with material design 
> and has no dependency on external JS.
> Vue-Gwt  :  GWT wrapper over Vue.js
>
> both are targeting GWT 3.0
>
>
>
>

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: The elusive J2CL

['Frank Hossfeld' via GWT Contributors]

That's not really true. There are a lot of people working on the GWT 
module, getting them out of GWT and moving them to standalone artifacts. 
Doing that, they replace JSNI with JsInterop, replace generators, etc. This 
is all done, to get GWT 2 ready for GWT 3. And if you want to see something 
existing in GWT 3, you can ask vertispan to do the job. 

With the knowledge about the things, that will change with GWT 3 / J2CL, I 
was able to make mvp4g ready for GWT 3 / J2CL. I replaced the generator 
with APT and remove the dependency to any GWT classes. I created a sample 
application based on the new version (mvp4g2) and Elemental 2. And yes, it 
works with J2CL. 

And, keep in mind, applications written in GWT in 2010 still work. What was 
the favorite JS framework at that time? I don't remember.

-- 
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/58442e48-3f55-4a55-8351-e39c5e368921%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Future of GWT

[Frank Hossfeld]

why takes it so much time? 

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Support for GWT 2.0.3, com.extjs.gxt 2.2.0-gwt2 with IE 11

[Frank Hossfeld]

Looking at the Versions Matrix, the only version of GXT that will work with 
GWT 2.8.2 is GXT 4.0.x.

Tale a look 
here: http://docs.sencha.com/gxt/4.x/guides/getting_started/Versions.html


Am Mittwoch, 21. Februar 2018 10:11:34 UTC+1 schrieb PRAJVAL POOJARI:
>
> Hey frank what would be a compatible version of gxt.. jar file for GWT 
> 2.8.2 ?
>
> On Thursday, 27 August 2015 05:45:57 UTC-4, Frank Hossfeld wrote:
>>
>> gxt-2.3.1a-gwt22 will work with GWT 2.7.
>>
>> Am Donnerstag, 27. August 2015 08:04:27 UTC+2 schrieb Narasimhulu Bysani:
>>>
>>> Till today we haven't faced any UI issues. Now we need to support our 
>>> application for IE 11. We tried to upgrade with GWT 2.7.0 and extjs gxt to 
>>> 3.x versions. But it is making our life miserable with lot of compilation 
>>> issues as GXT package structure was totally changed. I did came back to GWT 
>>> 2.6.0 and extjs gxt version to 2.3.1-gwt22, but finally i am getting below 
>>> error while compiling my code.Please let me know how to resolve below issue.
>>>
>>> [ERROR] Errors in 
>>> 'jar:file:/C:/Users/j1009306/.m2/repository/com/extjs/gxt/2.3.1-gwt22/gxt-2.3.1-gwt22.jar!/com/extjs/gxt/ui/client/widget/treepanel/TreePanel.java'
>>>[ERROR] Line 1634: The constructor El(Element) is undefined
>>> [ERROR] Errors in 
>>> 'jar:file:/C:/Users/j1009306/.m2/repository/com/extjs/gxt/2.3.1-gwt22/gxt-2.3.1-gwt22.jar!/com/extjs/gxt/ui/client/widget/form/HtmlEditor.java'
>>>[ERROR] Line 548: Type mismatch: cannot convert from 
>>> com.google.gwt.dom.client.Element to com.google.gwt.user.client.Element 
>>>
>>> On Wednesday, August 26, 2015 at 10:06:24 PM UTC+5:30, Thomas Broyer 
>>> wrote:
>>>>
>>>>
>>>>
>>>> On Wednesday, August 26, 2015 at 4:20:07 PM UTC+2, Narasimhulu Bysani 
>>>> wrote:
>>>>>
>>>>> please let me know to which versions i need to update GWT and GXT 
>>>>> versions ? 
>>>>>
>>>>
>>>> Any reason for not using the latest ones?
>>>>  
>>>>
>>>>>
>>>>> On Wednesday, August 26, 2015 at 1:38:54 PM UTC+5:30, Thomas Broyer 
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wednesday, August 26, 2015 at 8:35:00 AM UTC+2, Narasimhulu Bysani 
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Currently my application was developed with the combination of GWT 
>>>>>>> 2.0.3, com.extjs.gxt 2.2.0-gwt2 . Now we got a new requirement saying 
>>>>>>> that 
>>>>>>> it should support for IE 11. Please let me know the simple work around 
>>>>>>> to 
>>>>>>> achieve this task.
>>>>>>>
>>>>>>
>>>>>> Update GWT and GXT? 
>>>>>>
>>>>>

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT MVP Frameworks

[Frank Hossfeld]

I am one of the contributors of mvp4g. Yeah, that's right, mvp4g uses GIN. 
That's something I don't like, but trying to remove GIN is a breaking 
change. So we decided, as we startet with mvp4g2, to keep the numbers of 
dependencies small. mvp4g2 only uses Elemental 2 (Place management). It 
does not a have a dependecy to GWT! We replace the generators with APT. So, 
I would say, once it is ready to go, it should work with j2cl. 

Am Freitag, 13. Oktober 2017 16:00:57 UTC+2 schrieb hy:
>
> Is anyone using any GWT MVP based framework?
>
> We have been using GWTP, however the development on it seems to be stalled 
> and it still depends on GIN, which is also not under active development.
>
> GWTP is extremely powerful, however a lack of investment in it recently 
> has been concerning for us and we would like to be sure that our app is 
> future compatible.
>
> So, is there any other framework anyone is using out there that works like 
> GWTP and would take minimum transition (from GIN to Dagger, etc.); and has 
> a future compatibility (annotation processing, raw HTML, etc.).
>

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Using GWT libraries from J2CL

['Frank Hossfeld' via GWT Contributors]

I did not see any J2CL examples. Would be nice to know, how to replace the 
Entrypoint ...

Am Mittwoch, 31. Mai 2017 22:43:23 UTC+2 schrieb Goktug Gokdogan:
>
> J2CL doesn't require @JsType; JsType serves same purpose as in GWT.
>
> The likely steps required to make GWT library work with J2CL 
> (future-proofing) already described in multiple talks earlier but briefly; 
> no JSNI/JSO, no GWT.create, no generators and no com.google.gwt.* 
> references. This applies recursively to the library's deps as well.
>
> On Wed, May 31, 2017 at 1:29 PM, Anders Forsell  > wrote:
>
>> Hello,
>>
>> From the small examples of J2CL examples I have seen, the Java classes 
>> have been annotated with @JsType.
>> I understand that all Java code will be transpiled to ES6 JS classes with 
>> J2CL but can you refer/use other Java classes/libraries without adding 
>> specific annotations?
>>
>> More concretely, if I have a GWT/Java library will I be able to use that 
>> library with J2CL without modifying the source of it? 
>>
>> Thanks,
>>
>> Anders
>>
>> -- 
>> 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/3193454b-b4c7-428b-8a19-3e730601868f%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/905225df-a4c1-4ab8-a187-2b12f5b6a468%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.