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?
