Operating System: All
Platform: All

Hi SaintLee. Do you also put your yang schemas to cache schema folder?

(In reply to Jakub Morvay from comment #1)
> Hi SaintLee. Do you also put your yang schemas to cache schema folder?

yes,I think I do everythin right. Everything is fun when I use the Lithium version. I will push my change later,then let's see if it is appropriate.

(In reply to SaintLee from comment #2)
> (In reply to Jakub Morvay from comment #1)
> > Hi SaintLee. Do you also put your yang schemas to cache schema folder?
>
> yes,I think I do everythin right. Everything is fun when I use the Lithium
> version. I will push my change later,then let's see if it is appropriate.

I tried it now on a master branch and everything looks working fine. I used netconf test tool with default parameters as a device.

Here is my configuration data:
<ntopo:node xmlns:ntopo="urn:TBD:params:xml:ns:yang:network-topology"
xmlns:nctopo="urn:opendaylight:netconf-node-topology">
<ntopo:node-id>testtool</ntopo:node-id>
<nctopo:host>127.0.0.1</nctopo:host>
<nctopo:port>17830</nctopo:port>
<nctopo:username>admin</nctopo:username>
<nctopo:password>admin</nctopo:password>
<nctopo:tcp-only>false</nctopo:tcp-only>
<nctopo:yang-module-capabilities>
<nctopo:capability>
urn:opendaylight:mdsal:mapping:test?module=test&revision=2015-02-26
</nctopo:capability>
</nctopo:yang-module-capabilities>
</ntopo:node>

I also put relevant yang schema to karaf's cache/schema folder. Device connected successfully.

What exactly is your scenario?

Anyway, patches are always welcome. So, if you are working on this bug, you can also take it here in bugzilla (assign it to you).

SaintLee,

Are you specifying the schema-cache-directory in your scenario?

If so, there was a bug that is now fixed.
Else, please provide more information on how you do process to sideaload the schema as I tested it and it appears to work fine.

Thanks