As a result your property file will be copied at the root of your packaged jar.

Run sudo update-java-alternatives -s XXXX to set the XXX java version as default.
For Sun Java 6 this would be sudo update-java-alternatives -s java-6-sun

Run java -version to ensure that the correct version is being called.

Source: https://help.ubuntu.com/community/Java

From Java 1.6.

Thus you were probably quite frustrated when seeing that a GWT (Google Web Toolkit) client cannot send other requests than POST or GET.
Well here is the solution:

public class RequestBuilderForAnyHTTPMethodTypeExample extends RequestBuilder {

/**
* Constructor that allows a developer to override the HTTP method
* restrictions imposed by the RequestBuilder class. Note if you override the
* RequestBuilder's HTTP method restrictions in this manner, your application
* may not work correctly on Safari browsers.
*
* @param httpMethod any non-null, non-empty string is considered valid
* @param url any non-null, non-empty string is considered valid
*
* @throws IllegalArgumentException if httpMethod or url are empty
* @throws NullPointerException if httpMethod or url are null
*/
public RequestBuilderForAnyHTTPMethodTypeExample(String httpMethod, String url) {
super(httpMethod, url);
}


i.e. simply subclass the RequestBuilder

Source: (see the bottom of the page).

How not to use iterators:


while(views.iterator().hasNext()) {
View currentView = (View) views.iterator.next();
currentView.update();
}


Bing that basically crashed my Firefox (this is part of a GWT app) when running it as well as my Netbeans / GWT debugger. Notice that Firefox was so good to tell me that apparently the script I was running in a weird manner.

And it was indeed in an endless loop as you can guess: invoking the iterator() method returns a new Iterator object every time (which it is supposed to do, I’m the dumb one in that story). Thus, I was basically getting the same “next()” object every time and hasNext() was thus always true

Anyway that fixes it:


Iterator viewsIt = views.iterator();
while(viewsIt.hasNext()) {
View currentView = (View) viewsIt.next();
currentView.update();
}


Ok that was a trivial one, but actually so trivial that I just felt like shaming me a little more and publishing it here

Source ]]> http://www.guinard.org/~misterdom/2009/09/02/customize-author-netbeans-6-7/feed/ 0 http://www.guinard.org/~misterdom/2009/09/01/porting-gwt-nb/ http://www.guinard.org/~misterdom/2009/09/01/porting-gwt-nb/#comments Tue, 01 Sep 2009 10:09:47 +0000 misterdom http://www.guinard.org/~misterdom/?p=93 A while ago I was blogging about some experiences with the Google Web Toolkit (GWT) and Netbeans.
I reported on the existence of a great plugin (GWT4NB) that GWT-enables your Netbeans (starting from NB 6.5).
Well today I upgraded to NB 6.7 (from 6.5), to GWT4NB 2.6 (from 2.0.4) and to GWT 1.7 (from 1.5.3) and could not compile my GWT project anymore. Here are the steps I went through to make it run again:

1. Create an new empty Web project. When Netbeans asks you what framework you’d like to use (last sept of the wizard) select the Google Web Toolkit.
2. Be sure that the GWT Installation Folder points to the latest version of GWT (1.7 in my case).
3. Copy the content of both: build-gwt.xml and gwt.properties to these files in your old project.
4. Make sure you keep the entry gwt.module=... of your old project.
5. You might need to check the properties of the old project and make sure the “Frameworks” entry is referencing the latest version of GWT.

This should do, you should now be able to run and compile the old project with the latest GWT and GWT4NB plugin (at least it worked for me!).

The thing is the web is designed for English mainly and thus when getting the data out of my form in my Java servlet, I had to face the fact that all beautiful accents (e.g. é,à) of the French language were replaced by rather ugly and random chars.

After a number of attempts I eventually figured-out that changing the meta of the HTML page from:
...meta http-equiv="Content-Type" content="text/html; charset=UTF-8"...

to

.. http-equiv="Content-Type" content="text/html; charset=iso-8859-1"...

did the trick! Thanks ISO for not forgetting that English is not the only language that still exists on the web!