Hussein Terek

Check this http://programmergate.com/category/spring-boot/

If you return a clone instance from getAge(), then the caller will be accessing a completely separate instance of Age.

Hence the age of Alex will not be affected.

Seems to be interesting, would definitely check it.

Immutable classes are beneficial in any environment as you stated.

Most developers tend to relate immutability directly to multi-threaded environments because they can clearly see its advantages.

However, i consider it as one of the common design principles which should be achieved in any long-live software application.

Exactly, the main benefit of immutable classes is in multithreaded environments, where it's very costly to protect object state from concurrent modifications.

Agree with you

myInt is a field, it represents the object state and always stored in the heap as i mentioned in the article.

Variables are different from fields, they are normally defined inside methods and store some data. Like when you say:

public void test(){

int myInt = 2;

}

I didn't say it's different , you can pass static variables as method arguments noone can prevent you.

i am talking from best practices perspective, just wondering what's the point of passing it as method arguments if you already able to access it inside method scope. It's like passing an object and its fields together in method arguments. Hope you got my point

Can you explain more please ?

There is no specific handling for static variables when passed as method arguments, they are treated the same as normal variables.

my idea is why do you pass a PUBLIC static variable as method parameter if you're able to access it anyway through the class name, as if you pass an object along with its state in a method arguments this is nonsense too.

Good explanation, I agree.

Thanks Marcus.

I like how you explain "why overriding hashcode() alone doesn't force java to ignore memory addresses when comparing 2 objects". Good catch.

I'll definitely update my article to clarify this point.

Regarding my comment, I'm sorry if it looked bad to you, i just wanted to share my opinion and ask for your feedback.

I have no problem if you just delete it.

If 2 objects are equal, they must have the same hash code.

If 2 objects have the same hash code, it doesn't mean that they are equal.

Overriding equals() alone will make your business fail when working with hashing data structures like: HashSet, HashMap, HashTable. ...

Overriding hashcode() alone doesn't force java to ignore memory addresses when comparing 2 objects.

Check this tutorial.

Check this article to learn the most efficient way of structuring your web service application so that it's maintainable and open for future changes.

http://programmergate.com/web-service-project-structure/