You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
Hi! This is currently not possible. How would you expect this to work? Use the first server implementation that has a matching method name? Or use different url prefixes per server?
I have a collection of several JSON-RPC .json files which I would like to support in a single HTTP server. I have tried:
HttpServer
object for several different stubAbstractServer
child object constructorsAbstractServer
classes from my stubs which implement all their methodsFor both cases, it seems that only the last
AbstractServer
stub, which I include myHttpServer
object in, is taken into account. Calling methods from other stubs returns aMETHOD_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!
The text was updated successfully, but these errors were encountered: