Re: The GWT application hangs on the loading screen

[Craig Mitchell]

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/76e39f7a-8df0-4a7d-9d81-e14467b3764an%40googlegroups.com.

Re: Announcing GWT 2.10.1 and 2.11 releases

[Craig Mitchell]

Thank you Colin!  You're spot on, found 
it:  
https://mvnrepository.com/artifact/org.gwtproject/gwt-servlet-jakarta/2.11.0

> *Note that this is not compatible with running your jakarta-servlet app 
inside dev mode, but you will need to run your own server separately from 
dev mode. *

Thanks again.  Yep, I'm (now) running with SpringBoot 3 with Embedded 
Tomcat 10.

Cheers.

On Sunday 14 January 2024 at 1:12:03 pm UTC+11 Colin Alworth wrote:

> Craig, you’ll need to change to the -jakarta artifacts. That is, for 
> RemoteServiceServlet, instead of gwt-servlet.jar, use 
> gwt-servlet-jakarta.jar, and the class is in the .rpc.jakarta package to 
> ensure there is no possibility of referencing the wrong type. Change both 
> the jar and your imports to use it. 
>
> Note that this is not compatible with running your jakarta-servlet app 
> inside dev mode, but you will need to run your own server separately from 
> dev mode. 
>
> -- 
>   Colin Alworth
>   co...@colinalworth.com
>
>
> On Sat, Jan 13, 2024, at 7:54 PM, Craig Mitchell wrote:
>
> Awesome!  Thank you GWT team!
>
> Regarding:
>
> *> Added release artifacts for jakarta.servlet packages for both 
> RequestFactory and GWT-RPC.*
>
> When I look at com.google.gwt.user.server.rpc.RemoteServiceServlet, it's 
> still using javax.servlet.http.HttpServlet.  So calls 
> like getThreadLocalRequest() return javax.servlet.http.HttpServletRequest 
> and not jakarta.servlet.http.HttpServletRequest.  Is there another version 
> of RemoteServiceServlet I can use that uses the jakarta classes?
>
> Thanks.
> On Friday 12 January 2024 at 1:28:05 am UTC+11 Filipe Sousa wrote:
>
> 
>
> On Tuesday, January 9, 2024 at 9:36:08 PM UTC Colin Alworth wrote:
>
> I'm excited to announce the release of 2.10.1 and 2.11.0! This is our 
> second release under the new groupId, be sure when you update to change 
> away from "com.google.gwt", as it will not get more updates.
>
> If you use GWT-RPC and JPA/JDO annotations in your project, we strongly 
> suggest updating at least to 2.10.1 as soon as possible. To ensure that 
> vulnerable projects are aware of any problem, compile warnings will be 
> emitted if a problem is detected, and the server will default to not 
> allowing any vulnerable RemoteService instances. See 
> https://github.com/gwtproject/gwt/issues/9709 for information on the 
> issue, how we're responding to it, and how any additional follow-up might 
> look.
>
> Other highlights:
>
>- Transitioned to GitHub pull requests for new contributions, with 
>nightly builds running on GitHub Actions.
>- Added release artifacts for jakarta.servlet packages for both 
>RequestFactory and GWT-RPC.
>- Tested support for running on Java 21. This is likely to be the 
>final minor release series to support running on Java 8.
>- Updated JRE emulation to support Java 11 for Collections, streams, 
>and more.
>
> See https://github.com/gwtproject/gwt/releases/tag/2.11.0 or 
> https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0 for 
> complete release notes.
>
> This release wouldn't have been possible without help from so many 
> contributors, including developers, testers, and sponsors. A short list of 
> the teams and individuals that directly brought us this release: Juan Pablo 
> Gardella, Rocco De Angelis, Frank Hossfeld, Manfred Tremmel, Jim Douglas, 
> Zbynek Konecny, Piotr Lewandowski, Axel Uhl, Thomas Broyer, Filipe Sousa, 
> Sandra Parsick, Jens Nehlmeier, Schubec GmbH, Tom Sawyer Software, 
> Insurance Insight Inc. Join us on the issue tracker 
>  or at our OpenCollective page 
>  to help make future releases 
> possible.
>
>
> -- 
> 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/cc9f18b3-1bfd-43f0-b2bc-e694a04f6fb5n%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/2b4f5616-d5a3-45aa-b248-c2defddf056bn%40googlegroups.com.

Re: Announcing GWT 2.10.1 and 2.11 releases

[Colin Alworth]

Craig, you’ll need to change to the -jakarta artifacts. That is, for 
RemoteServiceServlet, instead of gwt-servlet.jar, use gwt-servlet-jakarta.jar, 
and the class is in the .rpc.jakarta package to ensure there is no possibility 
of referencing the wrong type. Change both the jar and your imports to use it. 

Note that this is not compatible with running your jakarta-servlet app inside 
dev mode, but you will need to run your own server separately from dev mode. 

-- 
  Colin Alworth
  co...@colinalworth.com


On Sat, Jan 13, 2024, at 7:54 PM, Craig Mitchell wrote:
> Awesome!  Thank you GWT team!
> 
> Regarding:
> **
> *> Added release artifacts for jakarta.servlet packages for both 
> RequestFactory and GWT-RPC.*
> 
> When I look at com.google.gwt.user.server.rpc.RemoteServiceServlet, it's 
> still using javax.servlet.http.HttpServlet.  So calls like 
> getThreadLocalRequest() return javax.servlet.http.HttpServletRequest and not 
> jakarta.servlet.http.HttpServletRequest.  Is there another version of 
> RemoteServiceServlet I can use that uses the jakarta classes?
> 
> Thanks.
> On Friday 12 January 2024 at 1:28:05 am UTC+11 Filipe Sousa wrote:
>> 
>> 
>> On Tuesday, January 9, 2024 at 9:36:08 PM UTC Colin Alworth wrote:
>>> I'm excited to announce the release of 2.10.1 and 2.11.0! This is our 
>>> second release under the new groupId, be sure when you update to change 
>>> away from "com.google.gwt", as it will not get more updates.
>>> 
>>> If you use GWT-RPC and JPA/JDO annotations in your project, we strongly 
>>> suggest updating at least to 2.10.1 as soon as possible. To ensure that 
>>> vulnerable projects are aware of any problem, compile warnings will be 
>>> emitted if a problem is detected, and the server will default to not 
>>> allowing any vulnerable RemoteService instances. See 
>>> https://github.com/gwtproject/gwt/issues/9709 for information on the issue, 
>>> how we're responding to it, and how any additional follow-up might look.
>>> 
>>> Other highlights:
>>>  • Transitioned to GitHub pull requests for new contributions, with nightly 
>>> builds running on GitHub Actions.
>>>  • Added release artifacts for jakarta.servlet packages for both 
>>> RequestFactory and GWT-RPC.
>>>  • Tested support for running on Java 21. This is likely to be the final 
>>> minor release series to support running on Java 8.
>>>  • Updated JRE emulation to support Java 11 for Collections, streams, and 
>>> more.
>>> See https://github.com/gwtproject/gwt/releases/tag/2.11.0 or 
>>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0 for 
>>> complete release notes.
>>> 
>>> This release wouldn't have been possible without help from so many 
>>> contributors, including developers, testers, and sponsors. A short list of 
>>> the teams and individuals that directly brought us this release: Juan Pablo 
>>> Gardella, Rocco De Angelis, Frank Hossfeld, Manfred Tremmel, Jim Douglas, 
>>> Zbynek Konecny, Piotr Lewandowski, Axel Uhl, Thomas Broyer, Filipe Sousa, 
>>> Sandra Parsick, Jens Nehlmeier, Schubec GmbH, Tom Sawyer Software, 
>>> Insurance Insight Inc. Join us on the issue tracker 
>>>  or at our OpenCollective page 
>>>  to help make future releases 
>>> possible.
> 
> 
> -- 
> 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/cc9f18b3-1bfd-43f0-b2bc-e694a04f6fb5n%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/bb932383-0db9-45c5-a8f1-74bbc4f619eb%40app.fastmail.com.

Re: Announcing GWT 2.10.1 and 2.11 releases

[Craig Mitchell]

Awesome!  Thank you GWT team!

Regarding:

*> Added release artifacts for jakarta.servlet packages for both 
RequestFactory and GWT-RPC.*

When I look at com.google.gwt.user.server.rpc.RemoteServiceServlet, it's 
still using javax.servlet.http.HttpServlet.  So calls 
like getThreadLocalRequest() return javax.servlet.http.HttpServletRequest 
and not jakarta.servlet.http.HttpServletRequest.  Is there another version 
of RemoteServiceServlet I can use that uses the jakarta classes?

Thanks.

On Friday 12 January 2024 at 1:28:05 am UTC+11 Filipe Sousa wrote:

> 
>
> On Tuesday, January 9, 2024 at 9:36:08 PM UTC Colin Alworth wrote:
>
>> I'm excited to announce the release of 2.10.1 and 2.11.0! This is our 
>> second release under the new groupId, be sure when you update to change 
>> away from "com.google.gwt", as it will not get more updates.
>>
>> If you use GWT-RPC and JPA/JDO annotations in your project, we strongly 
>> suggest updating at least to 2.10.1 as soon as possible. To ensure that 
>> vulnerable projects are aware of any problem, compile warnings will be 
>> emitted if a problem is detected, and the server will default to not 
>> allowing any vulnerable RemoteService instances. See 
>> https://github.com/gwtproject/gwt/issues/9709 for information on the 
>> issue, how we're responding to it, and how any additional follow-up might 
>> look.
>>
>> Other highlights:
>>
>>- Transitioned to GitHub pull requests for new contributions, with 
>>nightly builds running on GitHub Actions.
>>- Added release artifacts for jakarta.servlet packages for both 
>>RequestFactory and GWT-RPC.
>>- Tested support for running on Java 21. This is likely to be the 
>>final minor release series to support running on Java 8.
>>- Updated JRE emulation to support Java 11 for Collections, streams, 
>>and more.
>>
>> See https://github.com/gwtproject/gwt/releases/tag/2.11.0 or 
>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0 for 
>> complete release notes.
>>
>> This release wouldn't have been possible without help from so many 
>> contributors, including developers, testers, and sponsors. A short list of 
>> the teams and individuals that directly brought us this release: Juan Pablo 
>> Gardella, Rocco De Angelis, Frank Hossfeld, Manfred Tremmel, Jim Douglas, 
>> Zbynek Konecny, Piotr Lewandowski, Axel Uhl, Thomas Broyer, Filipe Sousa, 
>> Sandra Parsick, Jens Nehlmeier, Schubec GmbH, Tom Sawyer Software, 
>> Insurance Insight Inc. Join us on the issue tracker 
>>  or at our OpenCollective page 
>>  to help make future releases 
>> possible.
>>
>

-- 
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/cc9f18b3-1bfd-43f0-b2bc-e694a04f6fb5n%40googlegroups.com.

Re: Is moving away from RPC a good idea?

[Paul Robinson]

One thing I really like about using JSON for my message formats is that
they are human readable (YMMV).

If you're wondering whether a problem is client side or server side, or
when you just want to know exactly what information the client was given,
being able to read the content of messages can be very useful.

Paul

On Sat, 13 Jan 2024, 13:08 Alex Karg,  wrote:

> gwt-rpc is one of the parts I like the most about GWT and why we chose GWT
> to start with. Same DTOs on client and server and you don't have to care
> (too much) about de/serialization. Why do I care about JSON, or binary or
> whatever serialized format, as long as it is secure, performant and
> serialization is able to handle my object relation structures?
>
> Some mention "some annoying downsides" or "is imperfect in a lot of ways"
> regarding gwt-rpc. What are does? The only argument I understood so far, is
> that it may require you to have gwt-rpc *and* REST/RequestFactory
> client-server channels in parallel. We had that since the very beginning,
> because of OAuth, captcha, file download links etc.. I never saw any
> practical issues with that set up. For example with spring-security we can
> easily map both channels to the same user/roles/rights concept.
>
> On Wednesday, January 10, 2024 at 5:26:04 PM UTC+1 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-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/392768b6-58aa-4c71-b54f-cdb0d3aacf53n%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/CAGHNWN%2BHHwNkDxThecyGKDETUrskO%2BunCLbfGo5H21L94jZWcg%40mail.gmail.com.

Re: Is moving away from RPC a good idea?

[Alex Karg]

gwt-rpc is one of the parts I like the most about GWT and why we chose GWT 
to start with. Same DTOs on client and server and you don't have to care 
(too much) about de/serialization. Why do I care about JSON, or binary or 
whatever serialized format, as long as it is secure, performant and 
serialization is able to handle my object relation structures?

Some mention "some annoying downsides" or "is imperfect in a lot of ways" 
regarding gwt-rpc. What are does? The only argument I understood so far, is 
that it may require you to have gwt-rpc *and* REST/RequestFactory 
client-server channels in parallel. We had that since the very beginning, 
because of OAuth, captcha, file download links etc.. I never saw any 
practical issues with that set up. For example with spring-security we can 
easily map both channels to the same user/roles/rights concept.

On Wednesday, January 10, 2024 at 5:26:04 PM UTC+1 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-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/392768b6-58aa-4c71-b54f-cdb0d3aacf53n%40googlegroups.com.