[MDSAL-312] Split BindingGeneratorImpl into two classes Created: 23/Feb/18 Updated: 27/Mar/18 Resolved: 27/Mar/18 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | Binding codegen, Binding runtime |
| Affects Version/s: | None |
| Fix Version/s: | Fluorine |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Binding runtime and codegen are sharing BindingGeneratorImpl, but their expectations around it are a bit different:
We already have the beginnings of this split in the skinnyTypes flag passed to the constructor, but this needs to be extended so that we have three classes:
This also needs to be extended to TypeProviderImpl, so that we get rid of method comments from the runtime environment. The upshot from this is a leader BindingRuntimeContext and a faster SkinnyBindingGenerator, because the FullBindingGenerator will never be loaded at runtime.
|
| Comments |
| Comment by Robert Varga [ 03/Mar/18 ] |
|
Generator split: https://git.opendaylight.org/gerrit/69021 TypeProvider split: https://git.opendaylight.org/gerrit/69022 Disable pattern tracking: https://git.opendaylight.org/gerrit/69035
|