Currently, JsonRPCtoRPCBridge is using lower-level API (RequesterSession) to perform communication to remote ends. This is because exact interface it's not known at compile-time.

Generate interface on-the-fly (using ByteBuddy) based on resolved SchemaContext and replace communication with proxy API.