Just some questions about this issue:

(1). Could we modify the API generator and make it more generic, so it could be used for both core code and plugins?

[Maros]: Yes, we have to do it. JVpp classes are generated in a “singleton” way currently. So we need to restructure JVpp into a central JVpp registry + list of generated JVpp units. So from VPP we will get jvpp-registry and jvpp-core-api. Each plugin will provide its own jvpp-plugin-api. Each plugin-api will create its own jar to be used by Honeycomb.

(2).Could core code and plugins share the same connection or separate connections between JVPP and VPP?
[Maros]: We should use just a single connection and JVpp should manage it in its jvpp-registry.

[Maros]: Updating JVpp to be more modular should be straightforward, more interesting part is how we enable plugins to easily reuse JVpp generators + configuration.