-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
copy-config's RPC cxobj parameter does not contain namespace #131
Comments
I interpret this as |
* Only requests on the form: `<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><edit-config>...` will be accepted * All replies will be on the form: `<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">...` * Requests such as: `<rpc><edit-config>...` will not be accepted. * You can revert this behaviour (to clixon pre-4.6 behaviour) by enabling `CLICON_NAMESPACE_NETCONF_DEFAULT` * This API change is a consequence of: [copy-config's RPC cxobj parameter does not contain namespace #131](#131)
Fixed by patch above. Please verify. |
I hope to check this too tomorrow. |
@Topitzik did you checked it? |
the logs indeed show that the namespace arrived, but it seems to be stripped from the cxobj provided. |
Can you please provide some more detail on expected and actual behavior? |
here is an example: |
Thats because the callback is called with xe pointing to the rpc instance. If you use its parent, you will get the namespace, eg in gdb:
Also, at this point I usually use the function
|
ohh I didn't know xe had a parent. |
I take that as a resolve. |
copy-config RPC parameters are sent to the BE without namespace attribute (this is probably also the case with other netconf RPCs).
this is in contrast to the example RPCs in CLI client.
The text was updated successfully, but these errors were encountered: