-
-
Notifications
You must be signed in to change notification settings - Fork 318
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
Call method without parameters #134
Comments
Sounds to me like an error on the side of JSON-RPC.NET. If there are no parameters passed, the params field can be ommited. It is also in the JSON-RPC specification: http://www.jsonrpc.org/specification You should raise an issue at JSON-RPC.NEt about this. |
ok, but if server will by libjson-rpc-cpp server, what i must to do, to call method without parameters?
|
A try call method without parameters:
In server i get this request message: I test this case:
and get normal response with result of this method. but, in here http://www.jsonrpc.org/specification i find this example:
hm... okey i think i need fix fix and rebuild .net json rpc project... fix to parse message when params has no value. |
Yes, it is an error in the JSON-RPC.NET framework. You really should raise an issue there with your findings and reference this issue here. |
JSON-RPC.NET last commit was half year ago.. and author don't answer to users by last some issues. okey may be i will raise issue, but i haven't time for wait bug fix. |
omg... they fix this bug in one of the last commits, but don't refresh nuget package... |
I want call method from server
I use https://github.com/Astn/JSON-RPC.NET framework for server.
In client i need call method without parameters:
but i get
Exception -32602 : INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised: Invalid params, data: "The number of parameters could not be counted"
With use "params = Json::nullValue" i get same result.
How i can to call method without parameters?
P.s. when i call method with parameters I get normal result.
The text was updated successfully, but these errors were encountered: