[MDSAL-421] SchemaContextSingleton is only in controller but not in mdsal Created: 06/Feb/19 Updated: 16/Mar/19 Resolved: 16/Mar/19 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Michael Vorburger | Assignee: | Michael Vorburger |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
FTR https://git.opendaylight.org/gerrit/#/c/47770/ which introduced SchemaContextSingleton is only in controller but was not yet ported to mdal. |
| Comments |
| Comment by Robert Varga [ 13/Feb/19 ] |
|
vorburger I think SchemaContextSingleton prevents class-related state from being GC'd and introduces dependencies between tests. AbstractSchemaAwareTest performs automatic caching based on both the loading ClassLoader and the set of ModuleInfos going in. I think that solution is better as it applies to all users without having change their hierarchy. Is there a gap where that patch provides additional functionality? |
| Comment by Robert Varga [ 16/Mar/19 ] |
|
I don't think this class is necessary. |