Re: is it possible to debug GWT projects (breakpoints, step through code etc) ?

[Ralph Fiergolla]

Hi! Unless you want to invest time and effort in getting eclipse plugins up
and running, I would suggest using your browser's development tools
(Ctrl+Shift+I in Chrome/Edge) to debug the client side. Thanks to source
maps it will show your JAVA source code when debugging.
To debug the server side, you need to start your server with "-Xdebug
-Xrunjdwp:server=y,transport=dt_socket,address=8000,suspend=n" and create a
debug configuration to connect to port 8000 in Eclipse.
Good luck
Ralph

On Mon, Jun 24, 2024 at 11:19 AM 'Daniel Webb' via GWT Users <
google-web-toolkit@googlegroups.com> wrote:

> Hi,
> Is it possible to debug GWT projects - setting breakpoints and stepping
> through code? This would be server and/or client debugging.
>
> We've just had our internal GWT based app updated and it now uses maven to
> run (clean install appengine:run). The eclipse plugin based debugging
> technique that I used to use no longer seems to work.
>
> Thanks for any advice, I really like GWT but I'm lost as to how it all
> works!
> Daniel
>
> --
> 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/253e328a-484c-4c19-aaf7-e489780c3c0bn%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/CACwwWxMvZyndC3p8cqM7uKDDSck0khKeAVGLeUG2N2g-JXxJLw%40mail.gmail.com.

Re: Deploy to Google App Engine (GAE)

[Ralph Fiergolla]

Don’t want to build up pressure, but yeah that would come in very handy 😎

Craig Mitchell  schrieb am Fr. 23. Feb. 2024 um
00:05:

> I know it's outside of its scope, but it would be great if
> https://github.com/tbroyer/gwt-maven-archetypes had an example of "If you
> want to create an executable jar with Jetty, this is how you could do it".
> 🙂
>
> On Thursday 22 February 2024 at 5:30:51 am UTC+11 Tim Macpherson wrote:
>
>> I tried starting with the tbroyer archetype & to the server project I
>> added the app engine stuff from the Google sample to build the
>> appengine-staging dependencies directory.
>> Maybe all that should be in a separate project ?
>>
>> Sent from Yahoo Mail on Android
>> 
>>
>> On Wed, Feb 21, 2024 at 17:42, Thomas Broyer
>>  wrote:
>>
>>
>>
>> On Wednesday, February 21, 2024 at 3:11:54 PM UTC+1
>> tim_mac...@yahoo.co.uk wrote:
>>
>> I've been trying this app engine sample for Java 11+ which uses a JAR
>> packaged artifact that is installed locally:
>> it provides a Main class to instantiate an HTTP server to run an embedded
>> web application WAR file.
>>
>> github.com/GoogleCloudPlatform/java-docs-samples/tree/main/appengine-java11/appengine-simple-jetty-main
>> It has explicit jetty 11 dependencies.
>>
>> The WAR project is
>>
>> github.com/GoogleCloudPlatform/java-docs-samples/tree/master/appengine-java11/helloworld-servlet
>> The WAR is run in a local server with:
>> mvn exec:java -Dexec.args="../helloworld-servlet/target/helloworld.war"
>>
>> The problem I have is when I include GWT in the WAR project this draws in
>> Jetty 9 & other dependencies
>> which get copied to the cloud-deployment dependencies directory.
>>
>>
>> This means you WAR have dependencies on gwt-user and/or gwt-dev, that you
>> never want to deploy to a server. The WAR should have a dependency on
>> gwt-servlet only (or requestfactory-server).
>>
>> …and this is exactly what https://github.com/tbroyer/gwt-maven-archetypes
>> were meant to solve.
>>
>> --
>>
>> 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/c04ab91a-b898-489d-a509-6fafb9a363can%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/b4234f67-24c8-4028-8d27-be044a29c733n%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/CACwwWxM1fw8YGK7g4rYBxthQUz0%3DS5vPcZtRwTrHCFOOzYLpBg%40mail.gmail.com.

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

[Ralph Fiergolla]

Finally! Thanks a lot!

Thomas Broyer  schrieb am Mi. 24. Jan. 2024 um 19:57:

> oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at least
> Java 11.
>
> On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote:
>
>> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in
>> version 2024.1.24)
>>
>> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1
>> ma...@craig-mitchell.com wrote:
>>
>>> Ignore my post.  Just realised the doco uses net.ltgt.gwt.archetypes
>>> and not the springboot com.github.nalukit.archetype.
>>>
>>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta
>>> stuff.
>>>
>>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote:
>>>
 I was going to suggest the GWT doco gets updated to use this, but I see
 you already have!  https://www.gwtproject.org/gettingstarted-v2.html

 Excellent stuff!  👍

 On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote:

> Hi,
>
> both archetypes have been updated to the latest GWT (2.11.0) & Spring
> Boot version (3.2.2).
> Happy generating ...
>
> cu Frank
> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1:
>
>> Hi Grayson,
>>
>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released.
>> I'll try to take a look today.
>>
>> cu Frank
>>
>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52
>> UTC+1:
>>
>>> Hi Frank,
>>>
>>> Would you please also publish the new version for
>>> "modular-springboot-webapp" (the one that generates a gwt project with
>>> sample code)? The lastest verison of "modular-springboot-webapp" is 
>>> still "
>>> 2022.9.14
>>> "
>>> which is more than a year old.
>>>
>>> Thanks,
>>> Grayson
>>>
>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote:
>>>
>>> Happy new year! I just released a new version of the
>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The
>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17)
>>> with GWT 2.10.0 multi module project. Happy coding!
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/0c06d897-5654-49d8-871a-f10d8ea2d171n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACwwWxNg6bbc7Pd%3D823Dd24apHGfmboNgZ_%3Dh-1Q7O%3Dx8tLZjw%40mail.gmail.com.

Re: Is moving away from RPC a good idea?

[Ralph Fiergolla]

Fully agree - and very much like the example!

Leon Pennings  schrieb am Fr. 12. Jan. 2024 um
14:59:

> I think moving away from gwt-rpc is a bad idea.
> A big advantage of GWT is that I can code everything in java and do not
> have to serialize anything to and from text.
> That to me is one of the usp's of GWT.
> Going from java -> json -> java (or gwt java), is like trying to have a
> complex conversation between 2 Dutch guys, but with a German translator in
> between.
>
>
>
>
> Op donderdag 11 januari 2024 om 16:20:32 UTC+1 schreef Vassilis Virvilis:
>
>> Hi Vegegoku,
>>
>> Thanks for clearing that up.
>>
>> At some point I will definitely try the domino-rest/jackson.
>>
>> For now I dread the time I will eventually be forced to port my current
>> setup.
>>
>>
>> On Thu, Jan 11, 2024 at 5:13 PM Vegegoku  wrote:
>>
>>> The annotation on the POJO is not required at all, Domino-rest will auto
>>> generate the json-mapping classes if the jax-rs/jakarata resource
>>> consumes/produces a json even if the annotation is missing, so you can keep
>>> the POJO clean or only have Jackson compatible annotations. ;-)
>>>
>>> On Thursday, January 11, 2024 at 11:35:05 AM UTC+3 Vassilis Virvilis
>>> wrote:
>>>
 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.
>
>>

Re: Strategies for dealing with large number of languages?

[Ralph Fiergolla]

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/d483e663-1aa5-4bc7-a841-0660073c8a69n%40googlegroups.com.

Re: How to debug the java code on the eclipse ide with the tbroyer gwt maven plugin ?

[Ralph Fiergolla]

Yes, unfortunately the Eclipse plug-in is no longer maintained. Debugging
in the browser is the way to go! It works the same as for other JavaScript
frameworks (e.g. Angular) using a standard feature to map generated
JavaScript onto the source code (be it Java or Typescript etc.). That is,
you can set breakpoints and inspect the runtime values of your variables.
There is just one issue with variable names which differ between Java and
JavaScript but this is mostly cosmetic.

Marco Tenti (IoProgrammo88)  schrieb am Mo. 11. Dez.
2023 um 13:31:

> So this debug mode is deprecated
> https://www.gwtproject.org/doc/latest/tutorial/debug.html  ?
>
> When I launch the "gwt:codeServer" command, i  go to the sources panel of
> the browser chrome, and I can browse the code and set the breakpoints , but
> I can not "see" the runtime values of the variables as it happens with
> standard javascript is this correct ?
>
>  [image: ErrorPskCallStack.png]
>
> Il giorno lunedì 4 dicembre 2023 alle 13:30:37 UTC+1 Ralph Fiergolla ha
> scritto:
>
>> If I am not mistaken, you are mixing up things a little: the issue you
>> were looking at here
>> https://github.com/tbroyer/gwt-maven-plugin/issues/82 is not about
>> debugging the generated client part of your application, but about the
>> compiler that is actually generating the code you want to debug.
>>
>> To avoid wasting your time trying to set up the Eclipse Plugin I would
>> suggest using your browser's built-in development tools (Ctrl+Shift+I). You
>> will see your JAVA source code and can put your breakpoints etc. and step
>> through your code. This works in Chrome, Firefox, Edge.
>>
>> Bon courage
>> Ralph
>>
>> On Mon, Dec 4, 2023 at 1:16 PM Marco Tenti (IoProgrammo88) <
>> tenti...@gmail.com> wrote:
>>
>>> Hello everyone, I am updating some old gwt projects and I started to
>>> study about 15 days ago the gwt framework, this is to specify that I don't
>>> know all the secrets of the framework yet.
>>>
>>> Following Nalu's approach and starting from his example at
>>> https://github.com/NaluKit/nalu-examples/tree/main/nalu-simple-app-example,
>>> I was able to start with the gwt:codeserver both client and server part of
>>> my projects successfully.
>>>
>>> Unfortunately, I still haven't figured out what I need to do to
>>> enablethe  debugging on the client part of the project on the IDE eclipse.
>>>
>>> I've read in this issue
>>> https://github.com/tbroyer/gwt-maven-plugin/issues/82 a possible
>>> solution, but it doesn't seem to work, I'm 100% sure I'm doing something
>>> wrong myself., can anyone tell me looking at Nalu's example what additional
>>> commands I need to set to configure to debugging on the client java code in
>>> the eclipse ide ?
>>>
>>> --
>>> 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/3369c8a1-d86f-40de-9816-d35d865a1e4en%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit/3369c8a1-d86f-40de-9816-d35d865a1e4en%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/ed37a5ea-c5fa-4a74-9c37-3839311f410en%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit/ed37a5ea-c5fa-4a74-9c37-3839311f410en%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACwwWxMFQOg2pXm7W%3DZV1tHo2JJ7XEWV8VoovzqAb221YDBQ0w%40mail.gmail.com.

Re: How to debug the java code on the eclipse ide with the tbroyer gwt maven plugin ?

[Ralph Fiergolla]

If I am not mistaken, you are mixing up things a little: the issue you were
looking at here https://github.com/tbroyer/gwt-maven-plugin/issues/82 is
not about debugging the generated client part of your application, but
about the compiler that is actually generating the code you want to debug.

To avoid wasting your time trying to set up the Eclipse Plugin I would
suggest using your browser's built-in development tools (Ctrl+Shift+I). You
will see your JAVA source code and can put your breakpoints etc. and step
through your code. This works in Chrome, Firefox, Edge.

Bon courage
Ralph

On Mon, Dec 4, 2023 at 1:16 PM Marco Tenti (IoProgrammo88) <
tentimar...@gmail.com> wrote:

> Hello everyone, I am updating some old gwt projects and I started to study
> about 15 days ago the gwt framework, this is to specify that I don't know
> all the secrets of the framework yet.
>
> Following Nalu's approach and starting from his example at
> https://github.com/NaluKit/nalu-examples/tree/main/nalu-simple-app-example,
> I was able to start with the gwt:codeserver both client and server part of
> my projects successfully.
>
> Unfortunately, I still haven't figured out what I need to do to enablethe
> debugging on the client part of the project on the IDE eclipse.
>
> I've read in this issue
> https://github.com/tbroyer/gwt-maven-plugin/issues/82 a possible
> solution, but it doesn't seem to work, I'm 100% sure I'm doing something
> wrong myself., can anyone tell me looking at Nalu's example what additional
> commands I need to set to configure to debugging on the client java code in
> the eclipse ide ?
>
> --
> 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/3369c8a1-d86f-40de-9816-d35d865a1e4en%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/CACwwWxN-%2Bzg8L%2Bm%2B074hfoY09XUgR2qvCPSPbtMO71JY9yjgYQ%40mail.gmail.com.

Re: Unable to run project on browser

[Ralph Fiergolla]

Hi!
What makes you think this has anything to do with GWT? Your application is
not dependent on the browser.
Cheers
Ralph

Serena Roin  schrieb am Di. 7. Nov. 2023 um 13:34:

> Being that GWT is unsupported on the recent browsers, and my PC has
> natively Windows 11, I've tried to launch my project on Edge with Internet
> Explorer compatibility, but it gets some problems.
> On my older PC I had downloaded Firefox 24.0.3, but now on this PC I get
> "ssl_error_no_cypher_overlap" error. I've tried the main solutions on the
> net, like the one proposed in
> https://kinsta.com/blog/ssl_error_no_cypher_overlap/#:~:text=The%20SSL_ERROR_NO_CYPHER_OVERLAP%20error%20occurs%20when,Sockets%20Layer%20(SSL)%20protection
> .
> Anything seems to work to launch this project on any browser, do you have
> any solution?
>
> Serena
>
> --
> 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/e97d31ea-28ea-412e-aa49-07e60b13cb4en%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/CACwwWxNG%2BRE8p6Oam5Hoof1EW55_DESAOHehj0gujmCW2Ti%2BRw%40mail.gmail.com.

Re: GWT RPC call recognized as a Java Method Injection by Fortiweb

[Ralph Fiergolla]

That is, as long as I stay within GWT there is no need to change (and loose
type checking and convenience). I will happily stay with GWT RPC then!

R

Jens  schrieb am Mo. 24. Juli 2023 um 18:24:

>
> I think I asked the question before: as a long-term GWT-RPC user, what
> would be the benefit of moving to some other RPC protocol/mechanism?
>
>
> Depends on your situation of course. If you want to use your existing
> backend with other clients written in other languages then GWT-RPC is a bad
> fit. While the wire format of GWT-RPC is documented, you still need to
> write the client code to generate it. Also GWT-RPC supports inheritance
> which other languages you want to use might not support. Other JS based RPC
> solutions as well as general purpose solutions like gRPC typically do not
> support inheritance.
>
> GWT-RPC will already be annoying if you decide to have some portions of
> your app being written in a different framework since it is easier to find
> developers for that framework, e.g. angular, svelte, react, whatever. You
> would then need to define a JS api that calls into GWT code so these
> frameworks can talk to your GWT-RPC backend (or you need to provide new
> endpoints in your backend that do not talk GWT-RPC).
>
> -- 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/ab08b131-3904-49b1-8920-b924c7b31c9an%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/CACwwWxPMRKL%2Bk%3DBK-0P-e5xxykonSp7PAvMU0yQZdf1U6nzf6A%40mail.gmail.com.

Re: GWT RPC call recognized as a Java Method Injection by Fortiweb

[Ralph Fiergolla]

I think I asked the question before: as a long-term GWT-RPC user, what
would be the benefit of moving to some other RPC protocol/mechanism?

Thomas Broyer  schrieb am Fr. 21. Juli 2023 um 12:34:

>
>
> On Friday, July 21, 2023 at 11:38:59 AM UTC+2 petr...@o3enterprise.com
> wrote:
>
> We have one deployment of a GWT app where there is a Fortiweb firewall
> that blocks every GWT RPC call because it recognizes every call as a Java
> Method Injection attack. This seems to be caused by the presence of the
> pattern "java.lang." in the messages from the client to the server like the
> following:
>
> 7|0|7|https://host/app/app_gui/|BD9331DABCA5012FC56F3600DF03415F|com.app.gui.client.Bridge|getClientConfiguration|java.lang.St
> ring/2004016611|john|ADMINISTRATOR|1|2|3|4|2|5|5|6|7|
> 
>
> My idea is to convince the firewall administrator that these are
> false-positives as these calls are part of the GWT RPC mechanism that does
> not allow arbitrary java code execution on the server side.
>
> Is my reasoning correct or am I not worried enough?
>
>
> Your reasoning is correct. But you can also obfuscate type names to
> prevent triggering the WAF:
> https://github.com/gwtproject/gwt/blob/main/user/src/com/google/gwt/user/RemoteServiceObfuscateTypeNames.gwt.xml
>
> (disclaimer: I haven't used RPC for more than 10 years)
>
> --
> 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/40bf5948-5d59-4d47-8686-7b1db98e80fdn%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/CACwwWxPGRqV2pBTq4iPr4mmbE%2Bb38sxzAZuN%3D__z%2BemUACS5%3Dw%40mail.gmail.com.

Re: GWT compilation error with JDK 11

[Ralph Fiergolla]

It should not be that hard actually: you probably have separated client, 
shared and server side classes following the standard package naming 
convention. That is, basically it will be sufficient to copy your source 
code to the according client/shared/server sub projects and you are done. 
Okay, devil is in the details, but I did the same with some legacy project 
and happily live ever after. Give it a try. Definitely better than spending 
more time on installing different eclipse versions and plug-ins.
Cheers
Ralph 
On Tuesday, July 11, 2023 at 6:51:11 PM UTC+2 Ying Jin wrote:

> Ralph,
>
> Thanks for your suggestion. However, one of our GWT project in production 
> was developed long time ago and has very big codebase. I'm not sure how 
> hard to convert it to Maven oriented project. It seems that we have to do 
> lots of code refactoring 
> in order to separate client side and server side code and other 
> configuraitons. 
>
> thanks,
> Jenny
>
> On Monday, July 10, 2023 at 11:59:01 PM UTC-5 Ralph Fiergolla wrote:
>
>> Hi Jenny!
>> With all these issues related to out-dated Eclipse plug-ins I would 
>> strongly suggest switching to the new GWT Maven plug-in instead. Follow the 
>> instructions https://github.com/tbroyer/gwt-maven-archetypes/ to create 
>> a project that you can easily import into the most recent Eclipse (or any 
>> other IDE) subsequently. I don’t see much support for Eclipse plug-ins 
>> coming… I learned it the hard way too but am now happily working the Maven 
>> way. 
>> Bon courage!
>> Ralph 
>> On Monday, July 10, 2023 at 7:25:41 PM UTC+2 Ying Jin wrote:
>>
>>> Hi Colin,
>>>
>>> I posted this issue on the gwt plugin site below, but there is no reply 
>>> yet.
>>>
>>> https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/470
>>>
>>> In addition, I've tried to install other version of Eclipse such as 
>>> Eclipse 4.18 (2020-12) with a new workspace. After I installed GWT plugin 3 
>>> from market place and tried to create a sample gwt web application project 
>>> as described below in gwt site, I got the error " Invocation of 
>>> com.google.gwt.user.tools.WebAppCreator failed. See the error log for more 
>>> details."  It seems to me this current market place gwt plugin didn't work 
>>> as I didn't use our project at all
>>> and followed the tutorial below.
>>>
>>> https://www.gwtproject.org/usingeclipse.html
>>>
>>> Is there a way to get a working GWT plugin for Eclipse which can work 
>>> with JDK 11?
>>>
>>> Your help is much appreciated!
>>> Jenny
>>> On Tuesday, July 4, 2023 at 12:43:05 PM UTC-5 Colin Alworth wrote:
>>>
>>>> If the class can't be found, something is wrong with your gwt-dev, or 
>>>> the gwt-dev isn't on the classpath, or more details from the error message 
>>>> will indicate why the Compiler class couldn't be loaded. 
>>>>
>>>> Please file a bug with more details (logs, full error message, other 
>>>> details about differences between the working computer and non-working 
>>>> computer) at https://github.com/gwt-plugins/gwt-eclipse-plugin/ so 
>>>> contributors there can take a closer look?
>>>>
>>>> On Sunday, July 2, 2023 at 2:28:44 PM UTC-5 jiny...@gmail.com wrote:
>>>>
>>>>> I tried to reinstall Eclipse again and GWT 3 plugin again from Eclipse 
>>>>> market, downloaded and reinstalled gwt 2.9 for the project, however, I 
>>>>> still encountered the error below.
>>>>> It is so weird, the project configuration in eclipse works in my old 
>>>>> laptop, not in the new one though it both has windows 10 installed.
>>>>>
>>>>> Error: Could not find or load main class com.google.gwt.dev.Compiler
>>>>>
>>>>> eclipse-jee-2020-06-R-win32-x86_64
>>>>> GWT Plugin 3.0
>>>>> gwt-2.9.0
>>>>>
>>>>> Please see attached for the java build path dialog in eclipse.
>>>>>
>>>>> Any idea about resolving this error? Please help shed some light on 
>>>>> this problem.
>>>>>
>>>>> Your help is much appreciated!
>>>>> Jenny
>>>>>
>>>>>
>>>>> On Friday, June 16, 2023 at 3:25:42 PM UTC-5 Ying Jin wrote:
>>>>>
>>>>>> Thanks for your reply. Please see attached for the GWT lib specified 
>>>>>> in 

Re: GWT compilation error with JDK 11

[Ralph Fiergolla]

Hi Jenny!
With all these issues related to out-dated Eclipse plug-ins I would 
strongly suggest switching to the new GWT Maven plug-in instead. Follow the 
instructions https://github.com/tbroyer/gwt-maven-archetypes/ to create a 
project that you can easily import into the most recent Eclipse (or any 
other IDE) subsequently. I don’t see much support for Eclipse plug-ins 
coming… I learned it the hard way too but am now happily working the Maven 
way. 
Bon courage!
Ralph 
On Monday, July 10, 2023 at 7:25:41 PM UTC+2 Ying Jin wrote:

> Hi Colin,
>
> I posted this issue on the gwt plugin site below, but there is no reply 
> yet.
>
> https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/470
>
> In addition, I've tried to install other version of Eclipse such as 
> Eclipse 4.18 (2020-12) with a new workspace. After I installed GWT plugin 3 
> from market place and tried to create a sample gwt web application project 
> as described below in gwt site, I got the error " Invocation of 
> com.google.gwt.user.tools.WebAppCreator failed. See the error log for more 
> details."  It seems to me this current market place gwt plugin didn't work 
> as I didn't use our project at all
> and followed the tutorial below.
>
> https://www.gwtproject.org/usingeclipse.html
>
> Is there a way to get a working GWT plugin for Eclipse which can work with 
> JDK 11?
>
> Your help is much appreciated!
> Jenny
> On Tuesday, July 4, 2023 at 12:43:05 PM UTC-5 Colin Alworth wrote:
>
>> If the class can't be found, something is wrong with your gwt-dev, or the 
>> gwt-dev isn't on the classpath, or more details from the error message will 
>> indicate why the Compiler class couldn't be loaded. 
>>
>> Please file a bug with more details (logs, full error message, other 
>> details about differences between the working computer and non-working 
>> computer) at https://github.com/gwt-plugins/gwt-eclipse-plugin/ so 
>> contributors there can take a closer look?
>>
>> On Sunday, July 2, 2023 at 2:28:44 PM UTC-5 jiny...@gmail.com wrote:
>>
>>> I tried to reinstall Eclipse again and GWT 3 plugin again from Eclipse 
>>> market, downloaded and reinstalled gwt 2.9 for the project, however, I 
>>> still encountered the error below.
>>> It is so weird, the project configuration in eclipse works in my old 
>>> laptop, not in the new one though it both has windows 10 installed.
>>>
>>> Error: Could not find or load main class com.google.gwt.dev.Compiler
>>>
>>> eclipse-jee-2020-06-R-win32-x86_64
>>> GWT Plugin 3.0
>>> gwt-2.9.0
>>>
>>> Please see attached for the java build path dialog in eclipse.
>>>
>>> Any idea about resolving this error? Please help shed some light on this 
>>> problem.
>>>
>>> Your help is much appreciated!
>>> Jenny
>>>
>>>
>>> On Friday, June 16, 2023 at 3:25:42 PM UTC-5 Ying Jin wrote:
>>>
 Thanks for your reply. Please see attached for the GWT lib specified in 
 the java build path in Eclipse. I tried to compile it with JDK 8 and it 
 didn't work either. 
 The same project configuration in Eclipse worked in my old laptop, but 
 not in my new laptop. The Eclipse in the new laptop is a copy of the 
 Eclipse installed in the old laptop.

 In addition, I also tried to  copy the "gwt-dev.jar" from the old 
 laptop to the new one, but the compilation still gave me the following 
 error.

 Error: Could not find or load main class com.google.gwt.dev.Compiler

 The project was compiled by using GWT->Compile option provided by the 
 GWT Plugin installed in Eclipse.

 Version: 2020-06 (4.16.0)
 GWT Plugin version: 3.0

 Your help is greatly appreciated!

 thanks,
 Jenny
 On Friday, June 16, 2023 at 12:33:18 PM UTC-5 Colin Alworth wrote:

> GWT 2.9 should support running on Java 11, both running on JDK 11 and 
> compiling Java 11 sources.
>
> Without other information, it sounds like there is a problem with your 
> copy of gwt-dev.jar - the jar might be corrupt, or somehow not on your 
> classpath? 
>
> Can you verify that the jar is present and correct, and share more 
> specifics of how you are building?
>
> On Thursday, June 15, 2023 at 6:00:43 PM UTC-5 jiny...@gmail.com 
> wrote:
>
>> Hello,
>>
>> I tried to compile our GWT 2.9 project with JDK 11, but encountered 
>> the following error:
>>
>> Error: Could not find or load main class com.google.gwt.dev.Compiler
>>
>> Caused by: java.lang.ClassNotFoundException: 
>> com.google.gwt.dev.Compiler
>>
>> BTW, the Eclipse version is  Version: 2020-06 (4.16.0). 
>>
>> Please help shed some lights on this issue.
>>
>> thanks,
>> Jenny
>>
>

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

Re: App Server for GWT 2.10

[Ralph Fiergolla]

Hi!
GWT has no dependencies to any app server. Just use your preferred one (and
look into your own code if you experience issues ;-))
Bon courage
Ralph

Valavanur Man  schrieb am Di. 20. Sept. 2022 um 17:59:

> Hi,
>
> We are running GWT 2.8 with Glassfish4.  We had issues trying to run the
> GWT (2.8) App in Glassfish 6.
>
> Currently we are looking into upgrading to GWT 2.10. Would like you know
> what appservers are supported to run GWT 2.10 (even GWT 2.8 and beyond). Is
> there a recommended set of servers?
>
> Appreciate any pointers.
>
> 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/79044338-e2e5-4271-8f42-558aeb7c5481n%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/CACwwWxOFrVLCKA%2BnroN-REp%3DuzcLXJ0mYryfcsBEDxrt79WK-w%40mail.gmail.com.

Re: Add containers in NorthEast, NorthWest and Center section of BorderLayoutContainer

[Ralph Fiergolla]

Unless you want to create something based on css flex-layout and uibinder
yourself, it’s probably the easiest to combine 3 DockLayoutPanels (1 for
NE, E and SE, one for the center N and S, and finally one for the western
parts.

Abhishek Yadav  schrieb am Do. 15. Sept. 2022 um
23:13:

> Hi,
>
> Anybody has an idea about how to add containers in the northeast ,
> northwest and center section in north part of the BorderLayoutContainer.
>
> --
> 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/0f3f89e3-b419-4318-8151-5494d8f44f99n%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/CACwwWxPk5r%3DLe0FK6i%2BdktrMqGjxJRCE%2BTAwJz3zbCvn7%2B2K0g%40mail.gmail.com.

Re: Gxt/GWT Element has been deprecated

[Ralph Fiergolla]

@SuppressWarnings( "deprecation" )


Should do the trick, no?


Lorenzo Aditi  schrieb am Sa. 30. Juli 2022 um
16:42:

> I migrated to gwt 2.8.1 and I am using gxt 2.2.5
>
> I am using the method onRender from
> com.exts.gxt.ui.client.widget.LayoutContainer:
>
> *nRender*(com.google.gwt.user.client.Element parent, int index)
> 
>
> The issue is that *com.google.gwt.user.client.Element *was deprecated and
> replaced by *com.google.gwt.dom.client.Element.*
>
> So I am getting this warning Element in com.google.gwt.user.client has
> been deprecated
> 
>
> Is there a workaround to avoid this warning and keep using gwt 2.8.1 & gxt
> 2.2.5.
>
> 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/bebb78bb-2390-4c9f-a4e8-a6b264eb382fn%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/CACwwWxOji-6Haj-6ODai6%3DzZy-R8yhTg19ipo%2BwCMgM3BBYMcQ%40mail.gmail.com.

Re: GWT 2.10.0 release

[Ralph Fiergolla]

after cleaning up my projects a bit, migration from 2.9 completely 
transparent - great job!

On Monday, June 27, 2022 at 10:25:28 PM UTC+2 RT wrote:

> Great to see this progress. Updated my project to 2.10 from 2.9, the only 
> issue so far was removing the ie10 user agent in the gwt.xml, 
> leaving safari,gecko1_8
>
> On Saturday, June 25, 2022 at 1:33:25 AM UTC-5 blackh...@gmail.com wrote:
>
>> This is great, thnx
>>
>> Op donderdag 23 juni 2022 om 18:16:50 UTC+2 schreef nilo...@gmail.com:
>>
>>> I'm very happy to announce the release of GWT 2.10.0. This is the first 
>>> release using our new groupId, org.gwtproject, and the final release using 
>>> com.google.gwt. If you resolve dependencies from Maven Central, please be 
>>> certain that your project is using com.google.gwt:gwt (or 
>>> org.gwtproject:gwt) as a BOM, so that you are certain to have consistent 
>>> versions of gwt-user and gwt-dev, even across groupIds.
>>>
>>> For this release, either groupId will work, but future releases will 
>>> only be made on the org.gwtproject groupId.
>>>
>>> The zip download of the GWT SDK is available at 
>>> https://github.com/gwtproject/gwt/releases/download/2.10.0/gwt-2.10.0.zip
>>>
>>> --
>>>
>>> Release notes for GWT 2.10.0, taken from 
>>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
>>>
>>> Highlights 
>>>
>>>- 
>>>
>>>Updated to HtmlUnit 2.55.0 and Jetty 9.4.44. With this newer 
>>>HtmlUnit build comes support for Promise in unit tests, and the browser 
>>>strings that can be specified when running tests are “FF”, “Chrome”, 
>>> “IE” 
>>>(for IE11), “Edge”, and “Safari”.
>>>- 
>>>
>>>Tested support for running on Java 17, dropped remaining support for 
>>>running on Java 7.
>>>- 
>>>
>>>Maven groupId is formally changed to org.gwtproject, projects should 
>>>take care to make sure they are using either the old 
>>>com.google.gwt:gwt BOM or the new org.gwtproject:gwt BOM to sure 
>>>that Maven or Gradle correctly handle this change. This will be the last 
>>>published version using the com.google.gwt groupId.
>>>- 
>>>
>>>Dropped support for IE 8, 9, and 10.
>>>
>>> Bug fixes 
>>>
>>>- Correct Long.hashCode semantics
>>>- Support CLASSPATH environment variable when creating child 
>>>processes, fixing a bug where Windows could fail with a long list of 
>>>arguments.
>>>- Use Function.name instead of displayName to support visible method 
>>>names in Chrome 93+.
>>>- Allow stack traces to be available in Chrome when loading scripts 
>>>from a remote origin.
>>>
>>> JRE Emulation 
>>>
>>>- Added OutputStreamWriter emulation.
>>>- Support StringReader mark() and reset() methods.
>>>- Added StrictMath emulation.
>>>- Added BufferedWriter emulation.
>>>- Added incomplete PrintStream emulation.
>>>- Add Charset.defaultCharset() emulation.
>>>- Improve BigInteger emulated performance.
>>>- System.nanoTime() emulation with performance.now().
>>>- Added Optional.isEmpty emulation.
>>>- JRE Emulation improvements/simplifications to facilitate J2CL’s 
>>>WASM support. Note that these do not always offer specific improvements 
>>> to 
>>>GWT itself, but helps to keep the codebases consistent.
>>>
>>> Miscellaneous 
>>>
>>>- Add support to compile GWT itself in Java 9+.
>>>- Improve compiled code size for applications that never use 
>>>streams, by avoiding referencing streams from Throwable.
>>>
>>> For more detail, see the commit log 
>>> .
>>>
>>

-- 
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/f587af0c-0665-4a2c-811c-84f0472f713fn%40googlegroups.com.

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

[Ralph Fiergolla]

I consider this as the biggest advantage: you keep type-safety across
client/server calls. If you do some breaking changes, the compiler will
tell you! I definitely prefer this above finding out at runtime…
You can always achieve higher levels of flexibility by adding abstraction
layers between between hour client and server code - without loosing strict
type checking.

Rogelio Flores  schrieb am Mo. 23. Mai 2022 um
19:37:

> The big disadvantage that I see with gwt-rpc is that it ties your
> client-side with your server-side code (if you change anything related to
> your models/rpc on the client side, you also have to update your serve-side
> code, otherwise, it will not work). To me that in itself is a big
> disadvantage. With something like REST APIs, your client and server side
> code remain decoupled, giving you more freedom.
>
> On Friday, May 20, 2022 at 8:14:58 AM UTC-6 ralph.f...@gmail.com wrote:
>
>> why not use gwt-rpc? I am a lazy guy and am happily using it for more
>> than 10 years now - I even use the generated serializers in combination
>> with WebSockets. What can possibly go wrong here...?
>>
>> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>>
>>> Short answer: don't start using RequestFactory now, it's been
>>> practically unmaintained for years.
>>>
>>> Long answer: there's not really a longer answer actually, it's OK to
>>> keep using RF in existing projects (if you can't afford moving to something
>>> else), but don't start anything with it now.
>>> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>>>
>>> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>>>
 I know that GWT Request Factor plays an important role in Java object
 persistence and communication between client and server.
 However, on the server and client, even one object needs to generate
 related classes and interfaces, and then annotation settings etc. need to
 be set for each class and interface.
 It is complicated and has a lot of trouble to create.

 Originally, these things are like plugins, and it is desirable to
 select one object and generate a related class, but do you all know?

 I have been using GWT for over 10 years, but I do not use
 "RequestFactory" and operate only with objects like Map by RPC
 communication.
 This can simplify the entire system and greatly reduce the effort
 required to create it.

 GWT RequestFactory
 https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.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-tool...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%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/e3334aae-7ad4-49d9-8644-c2b6cfe9f065n%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/CACwwWxO9yB8OapamsQDx9yCtxu0T3Mwnaa0KRuXP0uf__rjdVw%40mail.gmail.com.

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

[Ralph Fiergolla]

why not use gwt-rpc? I am a lazy guy and am happily using it for more than
10 years now - I even use the generated serializers in combination with
WebSockets. What can possibly go wrong here...?

On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:

> Short answer: don't start using RequestFactory now, it's been practically
> unmaintained for years.
>
> Long answer: there's not really a longer answer actually, it's OK to keep
> using RF in existing projects (if you can't afford moving to something
> else), but don't start anything with it now.
> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>
> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>
>> I know that GWT Request Factor plays an important role in Java object
>> persistence and communication between client and server.
>> However, on the server and client, even one object needs to generate
>> related classes and interfaces, and then annotation settings etc. need to
>> be set for each class and interface.
>> It is complicated and has a lot of trouble to create.
>>
>> Originally, these things are like plugins, and it is desirable to select
>> one object and generate a related class, but do you all know?
>>
>> I have been using GWT for over 10 years, but I do not use
>> "RequestFactory" and operate only with objects like Map by RPC
>> communication.
>> This can simplify the entire system and greatly reduce the effort
>> required to create it.
>>
>> GWT RequestFactory
>> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.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/66b91749-8cb7-4b84-964d-82c2996adca8n%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/CACwwWxMAOGGV6xGpvq7nzW%3D29cOMGE0%2B6KA7B1UVRhgqa4_%3DyQ%40mail.gmail.com.

Re: Maven - Tomcat and devmode

[Ralph Fiergolla]

Hi! 
Seems like every long-time GWT user eventually comes to the point when 
suddenly the ECLIPSE plugin (or any other familiar setup) stops working... 
Without wasting too much time on trying to understand MAVEN I would suggest 
forgetting about webAppCreator and the gwt:devmode integrated Jetty 
Launcher!
The way to go for me was switching over to Thomas' GWT maven plugin: 

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

1. generate the project from 
scratch 
https://github.com/tbroyer/gwt-maven-archetypes/#start-the-development-mode
2. start 
debugging 
https://github.com/tbroyer/gwt-maven-archetypes/#start-the-development-mode

up to now I try to stay clear of those breaking JEE changes that come with 
TOMCAT10.

Good luck and have an eye on 
this: https://github.com/Vertispan/j2clmavenplugin

Ralph

On Wednesday, May 18, 2022 at 2:06:42 PM UTC+2 blackh...@gmail.com wrote:

> Hi everyone,
>
> We have been working with GWT and ant script for a long time.
> Now we are moving towards jdk 17 and are struggeling with devmode and the 
> jetty server.
>
> I read that if we want to run with devmode, we need to switch to maven en 
> deploy to our own webserver. This is Tomcat 9 or 10 for us.
>
> I have Created the MyWebApp with the webAppCreator and the maven options, 
> to see how the maven config looks like.
> This config works with the build in jetty, when running gwt:devmode.
>
> When i import the project in eclipse and use it as a web application, i 
> get the same issue as described here:
> https://itecnote.com/tecnote/eclipse-running-gwt-on-tomcat-in-eclipse/
>
> The suggestion there is to use -noserver, but no explanation on how to set 
> this.
> Attached is the generated pom file, how to change it so that it works with 
> devmode and tomcat?
>
> thnx
>
>
>

-- 
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/4bf2ae2e-cb90-4e79-9436-927be0f6c611n%40googlegroups.com.

Re: Just saying thanks

[Ralph Fiergolla]

I agree without reservation! Using GWT since 2011 and really glad to see
the 2.9 release working!


Tom Van Eetvelde  schrieb am Mo. 19. Okt. 2020 um
12:54:

> Hi,
>
> I just wanted to say that I have been using GWT since 2009 and I never
> thought about sharing how much fun GWT has brought to my developer life. So
> I am doing it now :-)
>
> To be honest, there are some libraries/toolkits out there that rise above
> the others. They have this intrinsic quality, they are open instead of
> restrictive on your coding style and when you need to take the extra mile
> in your dev work, the framework goes along, providing what you need. GWT is
> definitely among these.
>
> GWT is the reason that I started browser UI development as a Java backend
> profile.
> I am so happy GWT is still among us and I will be continuing to use this
> framework for many years to come.
>
> Thanks for this great framework!
>
> --
> 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/63a54346-f3fd-45b9-86d9-c1fe3ef9298dn%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/CACwwWxO-PhxVziYQQO4iQ919L4dz76C7JSXbS9y1zVtvyF%3DFpg%40mail.gmail.com.

Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06

[Ralph Fiergolla]

Stopped using Eclipse plug-ins just recently when going to JDK11. Am using
Maven Jetty plugin to run code server and host the application.

It was a bit cumbersome to set up (steep Maven learning curve!) but was
worth it in the end: onboard a new developer in no time (if Maven is
already configured).

Server side debugging in Eclipse (or whatever is your preferred IDE),
client side in Chrome or Edge.


Craig Mitchell  schrieb am So. 8. Aug. 2021 um
08:25:

> Tried a fresh Eclipse install, and also tried installing the GWT plugin
> without the Chrome debugger, and then adding the SDBG manually from here
> https://sdbg.github.io/ with no luck.
>
> Looks like the SDBG died somewhere between my old 2018-12 Eclipse, and
> 2021-06 Eclipse.
>
> Looking at the error:  javax/xml/bind/Datatypeconverter not found, it
> sounds like it's because Eclipse can no longer run on Java 8 (I'm running
> it on Java 11).
>
> Does anyone have Chrome debug in Eclipse still working?  Or are there any
> other plugins that we can use?
>
> On Saturday, 7 August 2021 at 2:46:30 pm UTC+10 Craig Mitchell wrote:
>
>> I just did a fresh install on a new PC, and the GWT plugin worked fine
>> with Eclipse 2021-06.
>>
>> The only issue I have is when I launch Chrome from Eclipse, Chrome opens
>> fine, however, I get this error:
>> [image: error.png]
>> and I can't debug the browser in Eclipse.  Debugging still works fine in
>> Chrome.
>>
>>
>> On Thursday, 17 June 2021 at 3:22:34 am UTC+10 Jim Douglas wrote:
>>
>>> I just updated my Eclipse development environment from 2021-03 to
>>> 2021-06. The installed GWT Eclipse Plugin (which hasn't been updated since
>>> 2017) no longer shows up in the menu bar, and it logs a bunch of errors. Is
>>> anyone (Brandon?) still maintaining it?
>>>
>>>
>>> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>>>
>>>   GWT Eclipse Plugin 3.0.0.201710131939
>>> com.gwtplugins.eclipse.suite.v3.feature.feature.group GWT Eclipse Plugin
>>>
>>>
>>> org.osgi.framework.BundleException: Could not resolve module:
>>> com.gwtplugins.gdt.eclipse.core [3649]
>>>   Unresolved requirement: Require-Bundle:
>>> com.gwtplugins.gdt.eclipse.platform
>>> -> Bundle-SymbolicName: com.gwtplugins.gdt.eclipse.platform;
>>> bundle-version="3.0.0.201710131939"; singleton:="true"
>>>com.gwtplugins.gdt.eclipse.platform [3651]
>>>  No resolution report for the bundle.  Bundle was not resolved
>>> because of a uses constraint violation.
>>>   org.apache.felix.resolver.reason.ReasonException: Uses constraint
>>> violation. Unable to resolve resource com.gwtplugins.gdt.eclipse.platform
>>> [osgi.identity; type="osgi.bundle"; version:Version="3.0.0.201710131939";
>>> osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]
>>> because it is exposed to package 'javax.servlet' from resources
>>> javax.servlet [osgi.identity; type="osgi.bundle";
>>> version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"] and
>>> jakarta.servlet-api [osgi.identity; type="osgi.bundle";
>>> version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"] via two
>>> dependency chains.
>>>
>>> Chain 1:
>>>   com.gwtplugins.gdt.eclipse.platform [osgi.identity;
>>> type="osgi.bundle"; version:Version="3.0.0.201710131939";
>>> osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]
>>> require: (osgi.wiring.bundle=javax.servlet)
>>>  |
>>> provide: osgi.wiring.bundle: javax.servlet
>>>   javax.servlet [osgi.identity; type="osgi.bundle";
>>> version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"]
>>>
>>> Chain 2:
>>>   com.gwtplugins.gdt.eclipse.platform [osgi.identity;
>>> type="osgi.bundle"; version:Version="3.0.0.201710131939";
>>> osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]
>>> require: (osgi.wiring.bundle=org.eclipse.jetty.servlet)
>>>  |
>>> provide: osgi.wiring.bundle; bundle-version:Version="10.0.5";
>>> osgi.wiring.bundle="org.eclipse.jetty.servlet"
>>>   org.eclipse.jetty.servlet [osgi.identity; type="osgi.bundle";
>>> version:Version="10.0.5"; osgi.identity="org.eclipse.jetty.servlet"]
>>> import:
>>> (&(osgi.wiring.package=javax.servlet)(&(version>=4.0.0)(!(version>=5.0.0
>>>  |
>>> export: osgi.wiring.package: javax.servlet
>>>   jakarta.servlet-api [osgi.identity; type="osgi.bundle";
>>> version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"]
>>> at org.eclipse.osgi.container.Module.start(Module.java:463)
>>> at
>>> org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1849)
>>> at
>>> org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
>>> at
>>> org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1842)
>>> at
>>> org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783)
>>> at
>>> org.eclipse.osgi.containe

Re: Lambda expression with GWT 2.9

[Ralph Fiergolla]

Works perfectly well. You might have to manually clean the compiler cache
from time to time though.

Hardik Shah  schrieb am Mo. 1. März 2021 um 13:13:

> Hi All,
>
> Can we write lambda expression code in GWT 2.9?
> With basic testing, look like it is working correctly. I search on
> stackoverflow and GWT project but not able to get it clearly.
>
> Regards
> Hardik.
>
> --
> 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/353ef10d-c381-4338-a06e-094abbc13ad2n%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/CACwwWxMiqMu9tFiTZUVMYBjx782XXPW5oBuBmFsT09SV5MS1Vg%40mail.gmail.com.

Re: Superdevmode and ReferenceErrors

[Ralph Fiergolla]

That made my day! I was encountering those issues a lot when using Lambda 
expressions - and renaming a Lambda is rather difficult... Thanks!

On Wednesday, February 24, 2021 at 10:36:38 PM UTC+1 David Nouls wrote:

> I just browse to the sdm website at http://localhost:9876 and click on de 
> button to clear the cache
> On 24 Feb 2021, 22:20 +0100, Stik , wrote:
>
> Aha, how do you clear the cache? i've never been sure where SDM is hiding 
> it 
> Stik
>
> On Wednesday, February 24, 2021 at 8:40:05 PM UTC David Nouls wrote:
>
>> It is a known issue with incremental compilation. It is annoying but I 
>> tend to just clear the sdm cache and reload.
>> On 24 Feb 2021, 20:50 +0100, Stik , wrote:
>>
>> Occasionally when running under SDM in Eclipse I will get a 
>> "ReferenceError: _g$ is not defined" from the browser.   The usual 
>> "fix" is to rename the symbol in question, reload, and the issue is gone.  
>>  If i then rename it back to what it used to be called, so nothing has 
>> actually changed, it remains fixed. 
>>
>> This happens to me maybe once a week or two when developing heavily.  
>> It's a minor irritation, but it's an irritation that's building up over 
>> time!   Has anyone else experienced this and found out a way to mitigate 
>> it?   I've never seen it happen to a full compile process, it seems to only 
>> affect SDM.  
>>
>> My gut feeling is that it affects static fields in particular, although 
>> i've seen it elsewhere (just now the constructor for an ordinary, dull 
>> class is missing).
>>
>> The problem is that it is not repeatable, it's something to do with the 
>> state of my SDM server at that particular moment, so I can't get a test 
>> case together to show to anyone
>>
>> Any thoughts?
>>
>> Stik
>>
>> --
>> 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/6c381234-9bb9-4ae7-b3c3-fd463a05c443n%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/52bbb484-79fa-4491-b8d8-2a73c30e0fb3n%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/6215c30b-2162-4ac8-a226-92daea2f5d65n%40googlegroups.com.

Re: How to start with GWT upgrade from version 2.1.0 to 2.9.0, (java 1.6 to java 1.8)

[Ralph Fiergolla]

While I never skipped so many versions with my own GWT applications, I 
would assume this upgrade to be mostly transparent and go without many code 
changes. Just replace the SDKs and check what your build process complains 
about (if it complains at all). 

On Tuesday, August 25, 2020 at 1:01:47 PM UTC+2 Hari wrote:

> Hi Team,
>
> (Apologies if the answers to my question are based on individuals opinion 
> based, but i am in dire need of your help)
>
> I am currently stuck with an old GWT 2.1.0 application written in Java 1.6 
> which needs to be updated to java 1.8, so we are planning to upgrade to 
> latest GWT version 2.9.0. There are no changes to the application code or 
> any new enhancement request in last 5 years, considering this our client is 
> expecting no changes to look and feel of the application but from the 
> compliance perspective we are required to upgrade to at least Java 1.8.
>
> But i have no experience and never used GWT, and there are very few guides 
> out there on upgrade from 2.1.0 to 2.9.0 (I know its a big jump). Can 
> someone help me understand, how to start the upgrade process, and how much 
> code changes would i need to make the application compatible with the new 
> version, will it be complete re-wright of the UI component of the 
> application? or will it be minor changes to existing code ? Finally, if the 
> upgrade requires complete re writing of UI component, is it worth it for me 
> to lean GWT (considering recent slow down in upgrades to GWT) and uses it 
> in the upgrade instead of complete rewrite of UI in React. 
>
> 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/53b65fe0-45c2-404f-8116-5946af5ba6can%40googlegroups.com.

Re: java.sql.Date - java.util.Date serialization issue

[Ralph Fiergolla]

I know it is quite some time ago since you posted this, but I just now 
(2020!) ran into the very same issue (using the very same workaraound). Is 
there any real solution for this by now?

On Tuesday, August 22, 2006 at 2:32:24 AM UTC+2, StudyBlue wrote:
>
> Casting 'non-serializable' objects to 'serializable' objects alone is
> not enough!
>
> 1.  According to the serialization documentation for the GWT,
> java.util.Date is serializable.
> (
>
> http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.RemoteProcedureCalls.SerializableTypes.html
> )
> 2.  According to the java docs, java.sql.Date is a subclass of
> java.util.Date.
> ( http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Date.html )
> 3.  According to you-can-look-it-up-yourself you can validly cast a
> subclass to the type of the superclass.
>
> Intuitively, you should be able to send java.sql.Dates across the RPC
> boundary simply by casting them.  Unfortunately, the reflection calls
> appear to look for the most specific type possible, not necessarily
> whatever it was cast to last.  (Maybe that's intended.  Maybe I'm
> totally off on my blind guess for what's causing this.)  No matter how
> I cast I java.sql.Date to java.util.Date, the call would always throw
> an exception claiming I was trying to send a java.sql.Date.  Eventually
> I got fed up with that and created a new java.util.Date from the
> java.sql.Date's getTime() method.  Creating an entirely new object
> solved the problem, but I'm assuming that's taking more time and
> processing than a simple cast.  If there's any way to make a sufficient
> cast, I'd love to hear it.
>
>

-- 
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/f971938a-06f4-403f-b737-161835da1bf8o%40googlegroups.com.