Re: [gwt-contrib] int vs Integer and the impact of "final"

2012-01-19 Thread Ray Cromwell
Final doesn't do much on classes or methods, since the compiler already detects when a method or class isn't overridden by anything else. Final on fields and parameters however is effective, because it lets the compiler assume those fields aren't written after the first assignment, which means the

Re: [gwt-contrib] int vs Integer and the impact of "final"

2012-01-19 Thread John Tamplin
On Thu, Jan 19, 2012 at 4:41 AM, Alexander Orlov wrote: > In Java, *Integer* is an object and can be set to null whereas *int *is a > primitive and cannot be set to null. > > In RequestFactory only the wrapped versions of primitives (= objects) are > allowed. So you might use *Boolean* and *Intege

[gwt-contrib] int vs Integer and the impact of "final"

2012-01-19 Thread Alexander Orlov
I've asked this question in the regular GWT group but I think this question is too specific for the regular group. ### In Java, *Integer* is an object and can be set to null whereas *int *is a primitive and cannot be set to null. In RequestFactory only the wrapped versions of primitives (= obje