Hi Jimin, The best way is we send a PR for protoStuff to provide the solution of listList/listMap, but it may not meet the needs of our release schedule. I don't think maintain a fork version of protoStuff is good way to go. If we can wrap the protoStuff and extends it ourselves, it may meet the needs of our release schedule.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Sep 15, 2018 at 9:36 AM wjm wjm <[email protected]> wrote: > > class Test { > public List<List<String>> listList; > public List<Map<String, String>> listMap; > } > > the field listList/listMap is invalid in protobuf. > ----------- > > currently we process this by protoStuff runtimeSchema, runtimeSchema > generated from Test class, and runtimeSchema can support the definition of > listList/listMap(that's protoStuff rule, not protobuf rule) > but because there are no classes in Edge service, currently we must dynamic > create new classes for protoStuff, that caused many problems. > > as we discussed before, we will not dynamic create new classes, just > serialize/deserialize by proto file, and proto file not support > the definition of listList/listMap > in this time, we must faced the compatible problem. > what's the best of our choice......
