I have implemented the following generic copy/equals method in our base Value Object. Any value object extending from the base class will not need to provide for the same.
I am contemplating making them final, coz I do not want any extending classes to override the implementation. But it then takes away the freedom providing alternate behavior.
Can anyone tell me, if this is the right way to go about and not make the methods final in the base VO?
The only reason I see for not making them final is as above and do we really have reasons for implementing different clone/equals in a project. I belive the behaviour for clone or equals is a project standard and we either have deep/shallow copies/equals.
Please let me know if otherwise. [ March 22, 2007: Message edited by: Devesh H Rao ]