[NETCONF-11] Netconf multiple notification streams Created: 04/Nov/14  Updated: 10/May/19

Status: In Progress
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Viera Zelcamova Assignee: Jakub Morvay
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


 Comments   
Comment by Robert Varga [ 13/Nov/15 ]

Move to NETCONFI project.

Comment by Alexis de Talhouët [ 12/Feb/16 ]

Does this mean current code base can subscribe to only one notification stream?

Comment by wu sandi [ 27/Sep/16 ]

Like NetconfNotificationManager.onNotitifcation method, as follow:
@Override
public synchronized void onNotification(final StreamNameType stream, final NetconfNotification notification) {
LOG.debug("Notification of type {} detected", stream);
if (LOG.isTraceEnabled()) {
LOG.debug("Notification of type {} detected: {}", stream, notification);
}

for (final GenericNotificationListenerReg listenerReg : notificationListeners.get(BASE_STREAM_NAME))

{ listenerReg.getListener().onNotification(BASE_STREAM_NAME, notification); }

}

the argment stream is not used by foreach block, and GenericNotificationListenerReg either doesn't override hashCode() method which extends from java.lang.Object. So it does't support multi stream publishers. Now When will this bug be resolved?

Generated at Wed Feb 07 20:13:56 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.