You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jake Farrell (Closed) (JIRA)" <ji...@apache.org> on 2012/03/14 02:04:43 UTC

[jira] [Closed] (THRIFT-1535) Why thrift don't use wrapped class for optional fields ?

     [ https://issues.apache.org/jira/browse/THRIFT-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jake Farrell closed THRIFT-1535.
--------------------------------

       Resolution: Duplicate
    Fix Version/s: 0.9
         Assignee: Jake Farrell

Duplicate of THRIFT-1528
                
> Why thrift don't use wrapped class for optional fields ?
> --------------------------------------------------------
>
>                 Key: THRIFT-1535
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1535
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Java - Library
>         Environment: any
>            Reporter: Ihor Mysak
>            Assignee: Jake Farrell
>            Priority: Minor
>             Fix For: 0.9
>
>
> JAVA only:
> in generated sources I see follow:
>   public double size; // optional
> so I need use two methods : double getSize() and boolean isSetSize() for use it.
> I guess you can change optional params on standard wrapped class: int -> Integer, double -> Double
> if value was uncheck -> null. one method one field, simple and easy

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira