cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Mehta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7290) VO classes shouldn¹t have any class variables declared as native type
Date Thu, 14 Aug 2014 03:41:12 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096514#comment-14096514
] 

Nitin Mehta commented on CLOUDSTACK-7290:
-----------------------------------------

We could but why create a confusion. Why not make all of them object types with no exception
? This makes it easier for someone to write new VO class without wondering when to make them
native type and when to make them object type. Its a clean implementation. I doubt some of
the VO classes might have followed that convention but later on this got muddled resulting
in bugs such as these.

> VO classes shouldn¹t have any class variables declared as native type
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7290
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7290
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.5.0
>            Reporter: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.5.0
>
>
> VO classes which are the mapping of schema to Java objects shouldn¹t
> have any class variables declared as native type. Because native types
> have default values whereas schema columns can be null and declaring as
> native types masks that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message