jvpp: stop plugin intialization on first mismatch 31/8831/2
authorMarek Gradzki <mgradzki@cisco.com>
Mon, 16 Oct 2017 10:33:12 +0000 (12:33 +0200)
committerDave Wallace <dwallacelf@gmail.com>
Mon, 16 Oct 2017 14:18:09 +0000 (14:18 +0000)
commitc7fc97ad85993956a5e76c2ea69dbd90b34360ac
tree34dcf0074b5c6b1f95e742af767f28bc9986f507
parentf90813d64c4d1aee3a51609e85e632b1f9a37536
jvpp: stop plugin intialization on first mismatch

Java bindings use get_message_id from jvpp-common
to detect if messages known at compile time
are avaliable at runtime.

In case of missing entry, Java exception is propagated
via JNI using (*env)->ThrowNew.

But this function does not end code execution so,
in order to prevent unexpected behaviour
(e.g. calling vl_msg_api_set_handlers with id == 0),
get_message_id caller should do it manually.

Change-Id: I2edb5013fd3658dcdd77a867b5cdf62e559ee071
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
src/vpp-api/java/jvpp-acl/jvpp_acl.c
src/vpp-api/java/jvpp-common/jvpp_common.c
src/vpp-api/java/jvpp-core/jvpp_core.c
src/vpp-api/java/jvpp-gtpu/jvpp_gtpu.c
src/vpp-api/java/jvpp-ioamexport/jvpp_ioam_export.c
src/vpp-api/java/jvpp-ioampot/jvpp_ioam_pot.c
src/vpp-api/java/jvpp-ioamtrace/jvpp_ioam_trace.c
src/vpp-api/java/jvpp-nat/jvpp_nat.c
src/vpp-api/java/jvpp-pppoe/jvpp_pppoe.c