[LISPMAP-184] Don't use NotificationListener in LISPMAP components Created: 06/Sep/23 Updated: 02/Jan/24 |
|
| Status: | In Review |
| Project: | lispflowmapping |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Ruslan Kashapov | Assignee: | Matej Šramčík |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Usage of generated interfaces extending org.opendaylight.yangtools.yang.binding.NotificationListener interface was deprecated for removal via In order to eliminate dependency on deprecated interface the affected logic require update to use org.opendaylight.mdsal.binding.api.NotificationService.Listener instead. Affected components: ./lispflowmapping/mappingservice/implementation/src/main/java/org/opendaylight/lispflowmapping/implementation/lisp/MapServer.java: notificationService.registerNotificationListener(this); ./lispflowmapping/mappingservice/implementation/src/main/java/org/opendaylight/lispflowmapping/implementation/LispMappingService.java: listenerRegistration = notificationService.registerNotificationListener(this); ./lispflowmapping/integrationtest/src/test/java/org/opendaylight/lispflowmapping/integrationtest/MappingServiceIntegrationTest.java: ((LispMappingService) lms).getNotificationService().registerNotificationListener( |