https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-167 yangtools <p>Enabling OF13 leads to following warnings to be emitted:</p> <p>2014-05-16 12:33:27.812 CEST <span class="error">&#91;fileinstall-./plugins&#93;</span> WARN o.o.y.s.b.g.i.LazyGeneratedCodecRegistry - Failed to find YANG SchemaNode for org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.multipart.request.multipart.request.body.MultipartRequestMeterConfigCase, with path SchemaPath [path=<span class="error">&#91;(urn:opendaylight:openflow:protocol?revision=2013-07-31)multipart-request, (urn:opendaylight:openflow:protocol?revision=2013-07-31)multipart-request-body, (urn:opendaylight:openflow:protocol?revision=2013-07-31)multipart-request-meter-config-case&#93;</span>, absolute=true] was not found in context.</p> <p>Operating System: All<br/> Platform: All</p> YANGTOOLS-167

Codec registry fails to lookup schema node

Bug Resolved Done Robert Varga Robert Varga Fri, 16 May 2014 11:33:33 +0000 Sun, 10 Apr 2022 18:35:06 +0000 Thu, 22 May 2014 08:34:42 +0000 0 2 <p>Turns out this is caused by SchemaContextUtil lookups, which prefer RPCs before notifications. OF protocol models have notifications and RPCs with the same name, so we enter the RPC lookup path, where we immediately fail and return that failure to caller.</p> <p>What we need to do instead is to try lookup in notifications (and groupings).</p> <p><a href="https://git.opendaylight.org/gerrit/7112" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/7112</a></p> Development External issue ID 1023 External issue URL Rank 0|i025jz: