[YANGTOOLS-167] Codec registry fails to lookup schema node Created: 16/May/14  Updated: 10/Apr/22  Resolved: 22/May/14

Status: Resolved
Project: yangtools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 1023

 Description   

Enabling OF13 leads to following warnings to be emitted:

2014-05-16 12:33:27.812 CEST [fileinstall-./plugins] 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=[(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], absolute=true] was not found in context.



 Comments   
Comment by Robert Varga [ 16/May/14 ]

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.

What we need to do instead is to try lookup in notifications (and groupings).

Comment by Robert Varga [ 16/May/14 ]

https://git.opendaylight.org/gerrit/7112

Generated at Wed Feb 07 20:52:27 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.