I think there are some edge cases where this might be problematic. Say you get a resource JSON back from a service and deserialize it into an object, where certain domain object fields have not been returned by the service (someField not included in the response). Then boolean getSomeField() should return null, but it can't. Right? ________________________________________ From: Jeremy Daggett [jeremy.dagg...@rackspace.com] Sent: Wednesday, July 09, 2014 11:59 AM To: dev@jclouds.apache.org Subject: Re: Primitive types in APIs?
No particular reason, just for consistency. ;) On 7/9/14, 9:40 AM, "Andrew Phillips" <aphill...@qrmedia.com> wrote: >> We need the APIs to be consistent. > >Any particular technical reason for this? Personally, I would be >tempted to say "boolean" when it can't be null, and @Nullable Boolean >otherwise, but that's just a somewhat context-free style preference. > >ap
