|
NPE appears when serializing BA DTO to BI Node in following case:
Three models are involved:
1. bgp-message.yang:
notification open
{ <<-- BA DTO represented by this model
uses open-message;
}
grouping open-message {
...
list bgp-parameters {
list optional-capabilities {
reference "http://tools.ietf.org/html/rfc5492#section-4";
container c-parameters {
...
2. bgp-multiprotocol.yang:
grouping mp-capabilities
{
...
}
augment "/bgp-msg:open/bgp-msg:bgp-parameters/bgp-msg:optional-capabilities/bgp-msg:c-parameters"
{
uses mp-capabilities; <<-- BA DTO includes this augmentation, that's the point where NPE occurs when serializing
}
3. bmp-message.yang:
grouping open-msg {
uses bgp-msg:open-message {
augment "bgp-parameters/optional-capabilities/c-parameters"
{
uses bgp-mp:mp-capabilities;
}
}
}
grouping peer-up {
...
container sent-open
{ <<-- the output (BI normalized node) represents this container
uses open-msg;
description
"The full OPEN message transmitted by the
monitored router to its peer.";
}
...
Note: Serialization is working as expected when the augmentation is not present in the DTO
| 
bug5524.zip
opendaylight-bug-5524-module1.yang