Use ApiPath in YangInstanceIdentifierDeserializer 42/97742/23
authorRobert Varga <robert.varga@pantheon.tech>
Mon, 4 Oct 2021 18:20:21 +0000 (20:20 +0200)
committerTomas Cere <tomas.cere@pantheon.tech>
Thu, 4 Nov 2021 14:35:01 +0000 (14:35 +0000)
commit6435e96118d7aea3e39ee65fd821be2c1880d262
treeff5cd67dcfff339c9eb29253cd14c50cc38b5ea3
parent791995cdf24c3623d5cfc76f6afab91ff4d3b873
Use ApiPath in YangInstanceIdentifierDeserializer

We are performing URL parsing in ApiPath, hence we can skip doing the
same thing in YangInstanceIdentifierDeserializer. This also improves
error reporting, as we provide additional info when we encounter parsing
errors. Error messages are also differentiated between parse errors and
semantic binding errors.

Escaping test has also updated, as ApiPathParser is intelligent enough
to understand both : and %3A in identityref name.

JIRA: NETCONF-631
Change-Id: I5fdb438d656b79199ea4bf316183d37280261eff
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
restconf/restconf-nb-rfc8040/src/main/java/org/opendaylight/restconf/nb/rfc8040/utils/parser/YangInstanceIdentifierDeserializer.java
restconf/restconf-nb-rfc8040/src/test/java/org/opendaylight/restconf/nb/rfc8040/utils/parser/YangInstanceIdentifierDeserializerTest.java