diff options
| author |   Matej Perina <mperina@cisco.com> | 2017-09-11 10:11:51 +0200 |
|---|---|---|
| committer |   Damjan Marion <dmarion.lists@gmail.com> | 2017-10-10 16:44:03 +0000 |
| commit | ac1a7286500c18ac51beb66e4a2b99ea26c8c966 (patch) | |
| tree | 62a4a0430bd0d5623c5e9945ca5bf671745351f9 /test/test_jvpp.py | |
| parent | d91c1dbdb31f80db7d967f2f57c43d0a81d65297 (diff) | |
jvpp: adding callbacks for all messages (VPP-914)
1) In the previous version callbacks were generated based on
request-replay naming conventions. It turned out they were too
strict in case of events (e.g. BFD sends Details messages as
notifications). So now we generate callback for all messages,
allowing to receive any message as notification.(callback_gen.py)
2) "notification" suffix is no longer added because all messages
are treated same (dto_gen.py, jvpp_c_gen_.py)
3) name of property that holds notification/events changed in callback
facade and future apis
4) JVppNotification.java is no longer used since all events are treated
equally
Change-Id: I13f6438affc3473040d63cd4acb3984d03e97482
Signed-off-by: Matej <matej.perina@pantheon.tech>
Diffstat (limited to 'test/test_jvpp.py')
0 files changed, 0 insertions, 0 deletions