I made the very troublesome discovery that different rules apply for Gwt to convert Java objects to JavaScript objects and using Java objects as parameters in Gwt's remote procedure calls (RPC). Following a list of issues arising when using Gwt RPC (but not in Java->JavaScript conversion)
The Maven Gwt Plugin is a powerful tool in developing Gwt applications using Maven Build Management. I have set up my development environment to code and run JUnit test in eclipse IDE (without using eclipse IAM etc but the Maven Eclipse Plugin instead), and I test gwt code using the
We have presented a paper at the 44th Hawaiian International Conference on System Sciences (HICSS) 2011. Below the links for the paper as well as the slides presented: Links Link to citation on citeulike Link to full text article on IEEE Xplore (requires subscription to the IEEE Xplore digital library)
I am working with the Maven Eclipse Plugin, the Maven Bundle Plugin and the eclipse PDE. A common activity in this setup is to refresh projects in the workspace, since the Maven bundle plugin generates new MANIFEST.MF files (which I copy via Maven Ant Task), which become "out
Direct evaluate Remote Procedure Calls (deRPCs) in GWT seem to be promising approach to transfer objects from server to browser. Rather than encoding objects into a stream of text in a legacy format, deRPC sends objects as JavaScript statements from server to client. However, after some time of working with
One of the strengths of GWT, from my point of view, is that large portions of the code (eg business logic) can be tested with plain old JUnit tests, without the slightest interference from servers, web browsers and other constraints. However, certain parts of the code must be tested in
Immutable objects are an easy yet powerful way to leverage some of the advantages of functional programming languages when writing plain old java. Such immutable objects declare all their attributes as final and are therewith protected from unforeseen state changes and side-effects. However, unfortunately the GWT RPC mechanism has problems
The Problem Sometimes you might want to include classes from a package in your gwt module, which are not in a sub-package of the package in which you have defined the Gwt module (MyModule.gwt.xml). For instance, you might have the following directory structure: /client/ClientService.java /browser/BrowserEntryPoint.
The Problem When developing an GWT application using Ext Gwt (GXT), various images are not displayed when opening the deployed .html file of your GWT project. These images may include: * borders of panels * backgrounds of panels * icons displayed when dragging and dropping components A panel, for instance, might look as
In the evolution of the Ext GWT (GXT) framework, there seemed to have been some change as to how selection events of trees/tree grids can be intercepted. In release 2.2.1, the following approach works: treeGrid.getSelectionModel().addSelectionChangedListener(new SelectionChangedListener() { @Override public void selectionChanged(SelectionChangedEvent se) { GWT.log(
The performance of a user interface based framework can often be a subjective matter. For me, for instance, the responsiveness of SmartGWT is slower than those of Ext Gwt (GXT), plain GWT 'feels' faster than GXT. However, such subjective measures are often quite unsatisfactory and might be wrong.
Although Java features an automatic garbage collector automatically clearing up unused objects and therewith unused memory, memory leaks can occur (and do occur from time to time). This is often caused by 'circular' references between objects. There are a few ways, to automatically test for memory leaks using
