Re: Wrapper Serialization with primitive field
On Jul 30, 10:50 am, Jimmy <jimmy_ple...@yahoo.com> wrote:
What's the advantage or disadvantage for having a wrapper to contain
primitive private member (i.e. private int count; // inside public
class Wrapper)?
Or is it better to not use primitive inside a serializable wrapper
(i.e. private Integer count; // inside public class Wrapper)?
Thanks for comment,
Jimmy
Generally, its better OO design to wrap primative values in a
meaningful class. Instead of "int distanceInMeters", you would have a
class Distance { private int meters; }, with the appropriate
getMeters() method. This allows you to decouple the actual storage
value (integer meters) with the representation (some Distance).
This allows you to change the Distance class to use, for instance,
centimeters or inches, without changing ANY code that references
Distance (the Distance class would do the necessary conversions in the
getMeter/setMeter methods, and you would add getInch/setInch, etc...)
As for serialization, this allows you to version the value as well.
You can intercept the serialization and do any necessary conversions
in one place, rather than having to do it for the same primitive value
in many places...
Using primitive values too often is sometimes known as the Primitive
Obsession code-smell (Refactorying, Martin Fowler).
If your value has a semantic meaning, and you don't have an
*overwhelming* reason not to, you should wrap your primitives in
meaningful classes.