Fix uninitialized ExtensionDefinition for openconfig-version 40/59240/2
authorIgor Foltin <igor.foltin@pantheon.tech>
Tue, 20 Jun 2017 14:01:17 +0000 (16:01 +0200)
committerRobert Varga <nite@hq.sk>
Mon, 26 Jun 2017 13:58:25 +0000 (13:58 +0000)
commit37c3705d7a7d6ad1df851c325f3401b0df9e8a74
treebed179512db88f046968855c4259203209cd694f
parent252c148537cd652fe0e0aeff14e3caceb9be0299
Fix uninitialized ExtensionDefinition for openconfig-version

The StatementDefinition for openconfig-version extension is
not bound to any revision. When populating the ExtensionNamespace
with openconfig-version, we have to store it with a revisionless
QName key. This way we can properly extract the corresponding
ExtensionDefinition later down the road in the
UnknownEffectiveStatementBase.

This issue causes NPE in MDSAL's binding generator v2.

Change-Id: Ie24c09b56986c87b5118d715ec6c8e755cf07ebe
Signed-off-by: Igor Foltin <igor.foltin@pantheon.tech>
yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/stmt/rfc6020/ExtensionStatementImpl.java