Simple example of iterating over struct lyd_node

[yogch]

I'm trying to parse a response I get using libnetconf2 and libyang. I could not find any simple example that's doing so.
I'm using nc_rpc_get(). Then I get an rpc and use nc_send_rpc(). Then I fetch the data using nc_recv_reply().
nc_recv_reply() gives me a libyang object which is called struct lyd_node* which should reflect (AFAIU) the data in yang.
The problem is that it just doesn't bring the data in data structures. I can only print it with lyd_any_value_str() and I get an xml. I can't really go over the nodes and see what is a container, what is a leaf and get that value.

What I'm asking is for a simple example of querying a server and then iterating over the results as if one node was list, then another was a leaf etc...

Thanks anyway!

[michalvasko]

Okay, so you get an anyxml node (which you can learn by examining struct lyd_node *node->schema->nodetype). If you cast it properly into struct lyd_node_any *, you will get 2 new members value and value_type. What you should get in libnetconf2 responses is value_type of LYD_ANYDATA_DATATREE. That means you can access value.tree, which is probably the data tree you are looking for.

[yogch]

Looks like lots of schemas fail :/
I'll try to check it out..

[yogch]

Well, I have no clue what's happening. :/

[INF]: Session 157: retrieving data for schema "ddd", revision "2016-07-10".
[INF]: Session 157: reading schema from server via get-schema.
[WRN]: Failed to load schema "ddd@2016-07-10".

This is specifically a very simple schema:

module ddd {
  namespace "http://ddd.com";
  prefix ddd;

  organization "DDD";
  description
    "This module is the parent module";

  revision 2016-07-10 {
    description
      "Initial release";
  }
}

There are other schema-load failures as well

[michalvasko]

It is strange that you do not see any other message so it is suspicious, libyang loads this module just fine. What versions are you using?

[yogch]

v2.0.7

[michalvasko]

For a quick fix, try using the latest v2 in the devel branch. It should be released officially soon.