I’ll translate:

“Which container/server to use (in Java). Tomcat and an XML-RPC servlet.”

Yes, something like that.

But JSON is different than XML-RPC in the sense that it does not define a protocol for procedure call.

JSON is the simplest way practically possible to serialize and deserialize objects for the most numerous network peers: JavaScript applications running in web browsers.

Yet nothing prevents you to apply it for RPC between HTTP peers.

Using URL’s and plain old HTML forms, send:

GET /object/method?name=world&… HTTP/1.0

Or post a JSON body:

POST /object/method
Content-type: application/json; charset=UTF-8

{”name”: “world”

and expect the following response:

HTTP/1.0 200 Ok
Content-type: application/json; charset=UTF-8

{”name”: “world”, “hello”: “Hello World!”}

Finally, the fact that JSON is a web protocol does not mean that it cannot be applied to transfer objects between other network applications than a web browser or server.