I have a collection of several JSON-RPC .json files which I would like to support in a single HTTP server. I have tried:
- Reutilizing the same
HttpServer object for several different stub AbstractServer child object constructors
- Creating a child class inheriting all
AbstractServer classes from my stubs which implement all their methods
For both cases, it seems that only the last AbstractServer stub, which I include my HttpServer object in, is taken into account. Calling methods from other stubs returns a METHOD_NOT_FOUND to the calling client.
Therefore I wanted to ask: is using several json-rpc stubs for a single httpServer (or any other AbstractServerConnector) a supported usecase of this library? If yes, any suggestions on how to implement it?
Thanks a lot!
I have a collection of several JSON-RPC .json files which I would like to support in a single HTTP server. I have tried:
HttpServerobject for several different stubAbstractServerchild object constructorsAbstractServerclasses from my stubs which implement all their methodsFor both cases, it seems that only the last
AbstractServerstub, which I include myHttpServerobject in, is taken into account. Calling methods from other stubs returns aMETHOD_NOT_FOUNDto the calling client.Therefore I wanted to ask: is using several json-rpc stubs for a single httpServer (or any other AbstractServerConnector) a supported usecase of this library? If yes, any suggestions on how to implement it?
Thanks a lot!