以下所有分析基于下方一个简单的IDL文件来分析。
service EchoService
{
string echo(1:string str);
}
类似的,thrift也会为每一个方法的参数生成一个类,默认的命名是:
方法名_args
生成的代码如下(省去一些不重要的地方)
public static class echo_args implements org.apache.thrift.TBase<echo_args, echo_args._Fields>, java.io.Serializable, Cloneable, Comparable<echo_args> {
//参数整体也是一个struct
private static final org.apache.thrift.protocol.TStruct STRUCT_DESC = new org.apache.thrift.protocol.TStruct("echo_args");
//struct的field,由方法的每一个参数构成
private static final org.apache.thrift.protocol.TField STR_FIELD_DESC = new org.apache.thrift.protocol.TField("str", org.apache.thrift.protocol.TType.STRING, (short)1);
private static final org.apache.thrift.scheme.SchemeFactory STANDARD_SCHEME_FACTORY = new echo_argsStandardSchemeFactory();
private static final org.apache.thrift.scheme.SchemeFactory TUPLE_SCHEME_FACTORY = new echo_argsTupleSchemeFactory();
public @org.apache.thrift.annotation.Nullable java.lang.String str; // required
//每一个参数对应的枚举,1是IDL文件中参数前的数字ID。”str“是形参的参数名
/** The set of fields this struct contains, along with convenience methods for finding and manipulating them. */
public enum _Fields implements org.apache.thrift.TFieldIdEnum {
STR((short)1, "str");
.......//一些不重要的部分
// isset id assignments
public static final java.util.Map<_Fields, org.apache.thrift.meta_data.FieldMetaData> metaDataMap;
static {
java.util.Map<_Fields, org.apache.thrift.meta_data.FieldMetaData> tmpMap