nimo frey wrote:
That deppends on who has the knowledge, who says that that object has to be updated? The User or the program?
The User can set the property too, instead of using a parameter..is it good to encapsulate all in properties instead of using obsolete parameters?
What do you mean with obsolete parameters?
I think both are correct, you have to think in the flow of your application and look who has to order the object to be updated.
nimo frey wrote:
I use Boolean because everyman says.."hey use the Wrapper Objects instead of primitive types"..I do not really know, when to prefer the one or the other. However, look at other programming languages such as scala where everything is (or should be) a object. So I use always the wrapper types, in this case Boolean instead of boolean. Is that bad?
I have never heard that about using the Object instead of the primitive, if you look at the Boolean class
http://java.sun.com/javase/6/docs/api/java/lang/Boolean.html it's doing references to the primitive type all the time.