Log In
Register
Forum
Topic RSS
13:43, EEST
January 27, 2012
Offline
I figured out that whenever an Event is subscribed, also a RefreshStartEvent and a RefreshEndEvent is triggered by the client.
When there is a need to provide fields in these System Events (e.g. NodeId, Stamp, …), how will a Listener for these events look like? Is there a method in an EventListener to hook in or do I need to implement such listener on top of all NodeManagers.
Thanks for any help.
Regards
14:30, EEST
December 21, 2011
Offline
These are kind of notification events that the events that are sent between them correspond to “currently active” events, so that the client can differentiate between the initial state and new change events after that.
You can basically just check the EventTypeId. I do not think that you need to define a separate listener for these events: they are special events that are sent for every subscription anyway.
In general, if you need to listen to “any events” from the server, you can listen to the Server object. If you want to filter only “normal” events and no Conditions, you would need to use something like “Not IsTypeOf(ConditionType)”
8:38, EEST
January 27, 2012
Offline
I figured out that method onConditionRefresh() of my EventListener is called when these refresh events are created. How will I get access to the corresponding RefreshStartEvent or EndEvent fields from either ServiceContext or Subscription, which are the 2 parameters for this method?
8:20, EEST
December 21, 2011
Offline
These events have no fields except for the EventType.
And you do not see these events in the EventListener.
This is the method in EventManager that does it:
Subscription subscription) throws StatusException {
fireConditionRefresh(serviceContext, subscription); // calls EventListener.onConditionRefresh
for (MonitoredItemBase item : subscription.getItems())
if (item instanceof MonitoredEventItem) {
final MonitoredEventItem eventItem = (MonitoredEventItem) item;
refreshStartEvent(eventItem);
try {
refreshItem(eventItem);
} finally {
refreshEndEvent(eventItem);
}
}
return true;
}
8:40, EEST
January 27, 2012
Offline
If I understand correctly, these events do not provide any fields except EventType. Even if I implement my own EventManager incl. overwriting method refresh using your snippet above, there will be no more fields to set for this kind of events.
14:10, EEST
December 21, 2011
Offline
Yes, they are just “indicator” events.
What would you like to do with them?
6:38, EEST
January 27, 2012
Offline
Well, I will do nothing with it 😉
It was a request by the client developer, because he figured out that these events do not provide data like Stamp or NodeId. However, as I also understand these events as only being “indicators” I will discuss with him why I should try to change these events.
Thank you.
Most Users Ever Online: 518
Currently Online:
21 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
hbrackel: 135
pramanj: 86
Francesco Zambon: 81
rocket science: 77
ibrahim: 76
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
fred: 41
Member Stats:
Guest Posters: 0
Members: 680
Moderators: 16
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1467
Posts: 6260
Newest Members:
sagarchau, elviralangwell4, Donnavek, Eddiefauth, DonaldPooma, fidelduke938316, Jan-Pfizer, DavidROunc, fen.pang@woodside.com, aytuleModerators: Jouni Aro: 1009, Otso Palonen: 32, Tuomas Hiltunen: 5, Pyry: 1, Petri: 0, Bjarne Boström: 983, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Jimmy Ni: 26, Teppo Uimonen: 21, Markus Johansson: 42, Niklas Nurminen: 0, Matti Siponen: 321, Lusetti: 0, Ari-Pekka Soikkeli: 5
Administrators: admin: 1
