Your informal guide to GWT
I've written a tutorial for GWT. Use it to create your first GWT app. Done? Good. Now that you have an application that greets you with a 'Hello World!', lets look into some concepts before further coding.
A modules will contain all the settings of your GWT project. Its defined in an XML with .gwt.xml extension. Referencing a module is very much like a java class.For example a module defined in the directory com/example/gwt/SomeModule.gwt.xml is referred as com.example.gwt.SomeModule
Typically a user defined module will inherit from com.google.gwt.user.User. But inheritance is optional and its not limited to one super module. You can inherit from as many modules as you wish. Its defined like:
Modules can define startup classes called as entry point class in GWT. The class should extend the com.google.gwt.core.client.EntryPoint interface, which defines only one method - onModuleLoad, where all your startup codes goes into.
Modules can also define another path called the public path. Like source path, these also contains resources accessed by the browser, but these resources are not meant for translation by GWT. Your images, css, Htmls go here.
When you implement GWT's RPC, you will be creating classes by extending RemoteServiceServlet. The URI mapping of those servlets are configured thru servlet tag. It has two attributes the class and path
<servlet class="com.example.gwt.server.MyRemoteService" path="/myRemoteService" />
All put together, your module file looks like this:
Coming soooooon. Stay tuned...
Coming soon. Stay tuned ...