[YANGTOOLS-192] Revisit way how modules lookup dependencies from old schemacontext Created: 19/Jun/14 Updated: 10/Apr/22 Due: 04/Jul/14 Resolved: 09/Jul/14 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Tomas Olvecky | Assignee: | Martin Vitez |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
When new yang file is parsed, instead of adding all imports, identities (maybe other statements as well) are inspected, and old modules are imported based on prefix. See org.opendaylight.yangtools.yang.parser.impl.YangParserImpl#findTargetModule(java.lang.String, org.opendaylight.yangtools.yang.parser.builder.impl.ModuleBuilder, java.util.Map<java.lang.String,java.util.TreeMap<java.util.Date,org.opendaylight.yangtools.yang.parser.builder.impl.ModuleBuilder>>, org.opendaylight.yangtools.yang.model.api.SchemaContext, int) method |
| Comments |
| Comment by Martin Vitez [ 01/Jul/14 ] |
|
Proposed patch: |