Home/ Questions/Q 9008103
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-16T01:51:47+00:00

I am new to GWT and understood the motive behind creating such good framework.

  • 0

I am new to GWT and understood the motive behind creating such good framework. However I could not understand how GWT builds the UI and shows while in development mode.

It is said that while bootstrapping .nocache.js file is loaded in the browser, then this file created a hidden iframe. Then depending on browser and language settings a .cache.html file is loaded in the iframe where all application logic resides.

What I could not understand is how gwt does this in development mode/ hosted mode. Because .cache.html files are not available in development mode. I assume that the sdk receives a request from .nocache.js file regarding the browser details and then generates a .cache.html file for that particular browser and that is loaded in the iframe. My question is how .nocache.js file sends a request to sdk to dynamically generate a .cache.html file? Or does it have something to do with hosted.html and the browser plugin? How the UI and RPC code is loaded while in development mode. For nocache.js file to send a request there must be a server program (Servlet) listening to the request and allowing GWt to start looking for entrypoint class and start generating the UI content.

I could not understand how gwt will come to know about the browser settings and generate the UI? Does hosted.html and browser plugin has something to do with the content generation?

I searched using google, but all my trials went useless. Or may be I searched using wrong search keys. Could anyone please tell me or point me to a link where it is clearly explained?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    When an application is running in development mode, the Java Virtual Machine (JVM) is actually executing the application code as compiled Java bytecode, using GWT plumbing to connect to a browser window.
    enter image description here

    As of GWT 2.0, development mode uses a regular browser instead of an embedded browser. You can use any supported browser.
    Out of process hosted mode (OOPHM) is an upcoming replacement for GWT hosted mode debugger. OOPHM allows one to use a standard browser (IE, Safari (32bit) and Firefox) for debugging GWT-client-side code.

    With OOPHM you can:

    • do modifications to your widgets with no time consuming Java-to-JavaScript recompilation
      set breakpoints to widget code.
    • use any advanced browser features and extensions not available in conventional hosted mode (Firebug for example).

    Useful links:

    https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDebugging

    http://code.google.com/p/google-web-toolkit/wiki/DesignOOPHM

    http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM

    http://www.slideshare.net/allahbaksh/gwt-generators-and-oophm

    Have a nice time.

    • 0