From 645c445d2815555e112c4cd4acba77fd7da9f224 Mon Sep 17 00:00:00 2001 From: Dan Newton Date: Tue, 16 Jul 2019 11:44:05 +0100 Subject: [PATCH] DOCS - Fix broken url to reconnecting rpc code (#5250) (#5278) (cherry picked from commit 2bfd2c8cb5c8ff894d63f825f58e893c44d3e432) --- docs/source/clientrpc.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/clientrpc.rst b/docs/source/clientrpc.rst index 144fa54ebc..bbc62bd9a6 100644 --- a/docs/source/clientrpc.rst +++ b/docs/source/clientrpc.rst @@ -368,11 +368,11 @@ The only way to confirm is to perform a business-level query and retry according In case users require such a functionality to write a resilient RPC client we have a sample that showcases how this can be implemented and also a thorough test that demonstrates it works as expected. -The code that performs the reconnecting logic is: `ReconnectingCordaRPCOps.kt `_. +The code that performs the reconnecting logic is: `ReconnectingCordaRPCOps.kt `_. .. note:: This sample code is not exposed as an official Corda API, and must be included directly in the client codebase and adjusted. -The usage is showcased in the: `RpcReconnectTests.kt `_. +The usage is showcased in the: `RpcReconnectTests.kt `_. In case resiliency is a requirement, then it is recommended that users will write a similar test. How to initialize the `ReconnectingCordaRPCOps`: