Rich Domain Model Q

[manifoldronin]

I absolutely agree that automatically adding getters/setters for all fields is just a bad thing. That being said, it seems to me that it'd be going too far toward the other extreme by automatically forbidding all the setters. If we all agree that some, if not most, objects in any domain model by their nature can never be immutable, why do we insist on making them so?

[Alarmnummer]

I absolutely agree that automatically adding getters/setters for all fields is just a bad thing. That being said, it seems to me that it'd be going too far toward the other extreme by automatically forbidding all the setters. If we all agree that some, if not most, objects in any domain model by their nature can never be immutable, why do we insist on making them so?

Replacing setters (like setSalary and setFireDate) by business methods (like fire or hire) doesn't lead to immutable objects.

[manifoldronin]

Replacing setters (like setSalary and setFireDate) by business methods (like fire or hire) doesn't lead to immutable objects.

Absolutely. My comment was directed to the OP's "I removed all the setters" part.

[Alarmnummer]

Absolutely. My comment was directed to the OP's "I removed all the setters" part.

Do you have idead about packaging? Personally I prefer to package by functionality and not by position in one of the layers.

[manifoldronin]

Do you have idead about packaging? Personally I prefer to package by functionality and not by position in one of the layers.

Me, too. Projects with packages like "controllers", "daos", "ejbs" are just depressing.