Re: Is moving away from RPC a good idea?

2024-01-15 Thread Cricri 
Finally I've decided to stick to RPC and use gwt-servlet-jakarta. We will
have a lot of applications (50+) to migrate to jakarta at some point, this
will be the fastest way.

Thanks all for your comments.

On Mon, 15 Jan 2024 at 11:26, Jens  wrote:

>
> Some mention "some annoying downsides" or "is imperfect in a lot of ways"
> regarding gwt-rpc. What are does?
>
>
> 1. Client and server always need to be in sync because of serialization
> policy. So a user must reload the web app if you redeploy your application
> and have modified shared classes.
> 2. If you want to use J2CL in the future you should not use it.
> 3. You can only use it with GWT clients unless you reimplement the wire
> format in other languages / applications. Only unofficial information about
> the wire format exists.
> 4. No async servlet support
> 5. Command pattern doesn't work well with GWT-RPC because you cannot code
> split the client side serialization data. So your initial or leftover
> fragment contains everything that goes over the wire. Code splitting only
> works well if you have one GWT-RPC service per code split condition.
>
> --
> 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/cc4b2a17-a072-4685-b138-34f31e46cc5fn%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/CABi7_98Pk%2BobtN2SiychHVx1sKpjqHW70-XH3pMXQ5pXgqTfQg%40mail.gmail.com.

Re: Is moving away from RPC a good idea?

2024-01-15 Thread Jens 


Some mention "some annoying downsides" or "is imperfect in a lot of ways" 
regarding gwt-rpc. What are does? 


1. Client and server always need to be in sync because of serialization 
policy. So a user must reload the web app if you redeploy your application 
and have modified shared classes. 
2. If you want to use J2CL in the future you should not use it.
3. You can only use it with GWT clients unless you reimplement the wire 
format in other languages / applications. Only unofficial information about 
the wire format exists. 
4. No async servlet support
5. Command pattern doesn't work well with GWT-RPC because you cannot code 
split the client side serialization data. So your initial or leftover 
fragment contains everything that goes over the wire. Code splitting only 
works well if you have one GWT-RPC service per code split condition.

-- 
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/cc4b2a17-a072-4685-b138-34f31e46cc5fn%40googlegroups.com.

Re: The GWT application hangs on the loading screen

2024-01-15 Thread '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

2024-01-15 Thread Antonio Capone 
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/fb4d716e-c5d1-480f-ad2d-778c80771d9en%40googlegroups.com.