There might be an error in the actual code of the app (exception or other).
I suggest you try some primitive debugging with a Window.alert message as
the first line of your onModuleLoad method.
ie...
@Override
public void onModuleLoad() {
Window.alert("App is starting");
On Wednesday, January 17, 2024 at 10:16:54 AM UTC-7 Antonio Capone wrote:
> Hi Frank, thanks for the support.
> No errors appear in the application logs of the application nor in the
> Develop Tool. The nocache.js file is successfully loaded. What else could
> it be?
>
> Regrds
>
> Il giorno lunedì 15 gennaio 2024 alle 15:15:56 UTC+1 Frank Hossfeld ha
> scritto:
>
>> 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() - 86400000L);
>>>> 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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/375583b8-8baa-49f4-b267-e2fb44568e3fn%40googlegroups.com.
