What's the difference between the strong type and weak type? >From the mail I can tell the weak type is useful in the edge service, can we just us it in the edge service?
BTW, We need to be care if there is a API break change, heading to version 2.0.0 is a good way, is there any other big change we need to make in the java-chassis 2.0.0? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Jan 30, 2019 at 8:39 PM wjm wjm <zzz...@gmail.com> wrote: > > currently, core mechanism is strong type > that caused to generate class dynamically in many special classloader, it's > dangerous: > > - need to generate almost all business classes in edge, maybe cause jvm > meta overflow > - unable to support advanced features of swagger, such as allOf > - caused some unnecessary data model convert > > > so we need to change core mechanism from strong type to weak type, we had > disscussed this before. > > the new problem is, because the two mechanism is not compatible, we must > make decisions about: > > - if plan it to be version 2.0.0 > - if we create branch for it > - if not create branch, then same functions will have two implements, > how to named the package > - if create branch, then i will replace old implement directly, that > cause compile problems > > any suggestion?
