[JSONRPC-58] Do not use RpcService in JSONRPC components Created: 03/Aug/23 Updated: 22/Jan/24 |
|
| Status: | Confirmed |
| Project: | jsonrpc |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Ivan Hrasko |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
A quick grep is showing these users of deprecated API: ./jsonrpc/provider/common/src/test/java/org/opendaylight/jsonrpc/provider/common/RemoteRpcInvokerTest.java: rpcReg = rpcAdapter.registerRpcImplementation(TestModelRpcService.class, new TestModelServiceImpl()); ./jsonrpc/provider/single/src/main/java/org/opendaylight/jsonrpc/provider/single/JsonRPCProvider.java: rpcReg = rpcProviderService.registerRpcImplementation(JsonrpcService.class, this); Convert them to new-style yang.binding.Rpc-based implementations. |
| Comments |
| Comment by Ruslan Kashapov [ 01/Sep/23 ] |
|
Following components require refactoring to eliminate direct usage of RpcService incl RpcConsumerRegistry.getRpcService(Class<? extends RpcService>):
|