<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Sanne Grinovero escribió:
<blockquote
cite="mid:50e5f6250812041301s3d255435p139a1949f7e8bfec@mail.gmail.com"
type="cite">
<pre wrap="">2008/12/4 Gavin King <a class="moz-txt-link-rfc2396E" href="mailto:gavin@hibernate.org"><gavin@hibernate.org></a>:
</pre>
<blockquote type="cite">
<pre wrap="">Sometimes you need null values, sometimes you don't. Java should let
you declare whether a value accepts null as part of the type
declaration (i.e. @Nullable Foo foo), and non-nullable should be the
default. But Java doesn't have this facility, so we just have to live
with it.
</pre>
</blockquote>
<pre wrap=""><!---->
A good practice should be to use "boolean" for not nullables (the primitive one)
as it can't be null; reserve the wrapper Boolean for values which can be null.
This has nothing to do with SQL of course ;-)
</pre>
</blockquote>
<br>
All right lets check the case of IsUserInRole.isUserInRole does it
really make sense to answer to the question: <br>
"Is user XXXX in role YYYYY?" with a null? if we are not sure, shoulnt
we default to "false" (or throw an exception?)<br>
</body>
</html>