[DAEXIM-17] Do not use RpcService in DAEXIM components Created: 03/Aug/23 Updated: 21/Dec/23 Resolved: 21/Dec/23 |
|
| Status: | Resolved |
| Project: | daexim |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Ľuboš Čičut |
| Resolution: | Done | 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: ./daexim/impl/src/main/java/org/opendaylight/daexim/impl/DataExportImportAppProvider.java: rpcReg = rpcProvider.registerRpcImplementation(DataExportImportService.class, this); ./daexim/impl/src/test/java/org/opendaylight/daexim/impl/DataExportImportAppProviderTest.java: when(rpcService.registerRpcImplementation(eq(DataExportImportService.class), any())) Convert them to new-style yang.binding.Rpc-based implementations. |