Correct, for instance, when calling ietf-netconf:commit, I use
curl -X POST \
http://localhost:8181/restconf/operations/network-topology:network-topology/topology/topology-netconf/node/NODE/yang-ext:mount/ietf-netconf:commit
\
-H 'accept: application/json' \
-H 'authorization: Basic YWRtaW46YWRtaW4=' \
-H 'content-type: application/xml' \
-d '<input xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
</input>
‘
This is due to the way RPC in working in ODL. Adding controller-dev as some
expert of RPC might provide a good explanation of the why the input is required,
even though nothing is in there.
Regards,
Alexis
> On Aug 2, 2017, at 10:44 AM, Allan Clarke <clar...@brocade.com> wrote:
>
> If you call an RPC that has all optional arguments with a payload like below,
> then your RPC gets invoked.
>
> { “input”: { } }
>
> If you call that RPC with an empty payload, you get an IllegalStateException.
> I believe this behavior is as intended, meaning that invoking RPCs with
> nothing is not allowed.
>
> Can anyone confirm this point-of-view?
>
> Many Thanks,
>
> Allan
> _______________________________________________
> netconf-dev mailing list
> netconf-...@lists.opendaylight.org <mailto:netconf-...@lists.opendaylight.org>
> https://lists.opendaylight.org/mailman/listinfo/netconf-dev
> <https://lists.opendaylight.org/mailman/listinfo/netconf-dev>
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
