Make Jayrock meet the error requirements of JSON-RPC 2.0

[atifaziz]

Originally reported on Google Code with ID 56

Given that JSON-RPC does not define the error object, but JSON-RPC 2.0 does, it would
be nice or interesting to encapsulate all exceptions thrown by an application with
a custom exception, as to make the JsonRpcError class return a correct JSON-RPC 2.0
error object.

e.g. as for now Jayrock returns an object like { "name", "error", "errors" } whilst
JSON-RPC 2.0 specification defines the error object as { "code", "message", "data"
}. I have edited somewhat the code of the application, and found that you can perfectly
define custom Exceptions with a code (and still treat basic Exceptions with a custom
"unknown Exception" code). This way you can offer a JsonException class to the user,
which could be inherited and the error code changed or something.

I marked this as an enhancement because the current error object meets JSON-RPC 1.0
requirements. 

Reported by jeamfry on 2014-05-20 04:23:07

[atifaziz]

Reported by azizatif on 2014-05-26 18:55:03

• Status changed: Accepted
• Labels added: Priority-Low, Component-JSON-RPC
• Labels removed: Priority-Medium

[atifaziz]

Here's an initial patch to resolve this issue. Please review it and make sure its good
for inclusion

Reported by RolfanRagnorak on 2015-01-29 16:31:13

---

- _Attachment: [jayrock_76_to_77.diff](https://storage.googleapis.com/google-code-attachments/jayrock/issue-56/comment-2/jayrock_76_to_77.diff)_

[atifaziz]

Uhm, dude? what's up with this?

Reported by RolfanRagnorak on 2015-05-26 13:29:20

[atifaziz]

@RolfanRagnorak Since Google has been so kind to shut down their project hosting service[1]
(instead of, say, just freezing it), I'm spending a lot time migrating my projects
as opposed to making actual progress on them. That's what's up.

[1]: http://google-opensource.blogspot.ch/2015/03/farewell-to-google-code.html

Reported by azizatif on 2015-05-26 16:50:36

[atifaziz]

@RolfanRagnorak I finally got round to reviewing your patch. Seems to me that @jeamfry
is looking for JSON-RPC 2.0 compliance on the server end for reported errors whereas
your patch addresses the issue on the client side.

Reported by azizatif on 2015-05-28 07:11:09

[rjune]

You are correct, my patches thus far have been on the client side. I don't use Jayrock for the server.