[
https://issues.apache.org/jira/browse/THRIFT-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669089#action_12669089
]
David Reiss commented on THRIFT-297:
------------------------------------
The reason that the standard ("non-beans") interface exists is that we didn't
want to mandate that application code use getters and setters for simple
structures. I think that it is a really good option and should not be
eliminated. Do you remember what the problem was with the generic
getter/setter for the standard interface? Is is just that you don't want to
return "empty" values if the thing is unset? I don't think there is a problem
with that. In the standard interface, we should take for granted that __isset
might not be accurate, and just give the application code access to the data.
> getFieldValue and setFieldValue should be abstract TBase methods
> ----------------------------------------------------------------
>
> Key: THRIFT-297
> URL: https://issues.apache.org/jira/browse/THRIFT-297
> Project: Thrift
> Issue Type: Improvement
> Components: Compiler (Java), Library (Java)
> Reporter: Nathan Marz
>
> Since these methods can be called on every TBase instance, they should be
> part of the TBase API. These methods are useful in conjunction with the meta
> data features.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
