3 Commits

Author	SHA1	Message	Date
Tibor Sirovatka	42bb61fd16	HONEYCOMB-67 Introduce exception handling into JVPP ... Send calls throws VppInvocationException on failure Failed requests (negative retval) reported over onError callback interface method Removed retval attributes from dto/xxxReply.java calls Change-Id: Ibd4e90c320d080e02d75b4bd056a7b11c8e37aa7 Signed-off-by: Tibor Sirovatka <tsirovat@cisco.com>	2016-06-09 02:22:34 +00:00
Marek Gradzki	d85036fd6b	HONEYCOMB-10: jVpp - the new java API. C code and jar file generation ... Added comments generation for C and Java files. Change-Id: Ifb670a5592eb871bfe68804f0a8d8f9b5b14f00a Signed-off-by: Marek Gradzki <mgradzki@cisco.com> Signed-off-by: Ed Warnicke <eaw@cisco.com>	2016-05-02 20:58:54 +00:00
Maros Marsalek	45a42b5d7f	HONEYCOMB-10: jVpp - the new java API. Java code generation ... The old japi has two main drawbacks: * it is not fully generated (requres manual coding for every new api call that returns data other thanstatus code) * it is not asynchronous from Java perspective (requires active wait loops - big overhead due to JNI boundary being crossed lots of times). The new api is lightweight (fully generated except for connect, disconenct and ping) and truly asynchronous (uses callbacks, utilities that offer java.util.concurrent.Future interface are also provided). Change-Id: I531080ef651e8a74f19210490c71d161221ab600 Signed-off-by: Marek Gradzki <mgradzki@cisco.com> Signed-off-by: Maros Marsalek <mmarsale@cisco.com> Signed-off-by: Ed Warnicke <eaw@cisco.com>	2016-05-02 08:46:21 -05:00