[MDSAL-435] Expose EffectiveModelContext from DOMSchemaService Created: 10/Apr/19 Updated: 23/Apr/20 Resolved: 09/Apr/20 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | DOM API |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0 |
| 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 |
|
We are currently exposing SchemaContext, which forces users to deal with SchemaNodes. In order to get migration to EffectiveStatements going we should expose EffectiveModelContext instead, so users can choose which API to use. |
| Comments |
| Comment by Robert Varga [ 19/Aug/19 ] |
|
It is also interesting note that NMDA is really dictating datastore-centricity, i.e. each datastore has its own SchemaContext (encapsulated in DatastoreContext in Yang Tools). This may mean that DOMSchemaService is either a more complicated beast or does not exist. |
| Comment by Robert Varga [ 30/Sep/19 ] |
|
Controller's DOMSchemaService is derived from our DOMSchemaService and we cannot use default methods (due to aries bug), hence we cannot make this transition in a reasonable way. Punt until controller is purged (Aluminium MRI). |