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
In Ext Gwt or GXT there are various ways to intercept drag and drop events directed at a Tree or TreeGrid. However, many of these do not necessarily lead to the expected results. There is also not much documentation of how to work with these events. 1. Implement the Interface
I just spend a while to find the right repository for the gwt-maven-plugin version 2.1.1-SNAPSHOT. To cut it short, one possible repository is: <pluginRepositories> <pluginRepository> <id>Codehaus Group Snapshots</id> <url>https://nexus.codehaus.org/content/groups/snapshots-group/
Really exiting about GWT is the promise to develop sleek user interfaces with Java; even the GWT UIs created out of the box look quite impressive when compared for instance, with a vanilla Swing interface. However, a number of frameworks help tremendously in unleashing the full capabilities JavaScript offers nowadays.
The Problem You want to exclude certain files and folders from being uploaded to the SVN repository in eclipse. However, some files in the project allow you to right-click them and select Team / Add to svn:ignore and for other files this action is 'greyed out'. The Solution
Both eclipse and the Netbeans IDE provide strong tool support for deploying applications based on their respective platforms. This includes supports for branding for instance with custom splash screens as well as creating executables for various platforms (Windows, Mac OS X, Linux). Eclipse allows to define Product configurations, which can
The Problem After generating an eclipse project using both the Maven Eclipse Plugin and the Maven Bundle Plugin (BND), eclipse warns that "build.properies does not exist". The Solution Maybe more a workaround than a solution but it is relatively simple to create the build.properties file manually