Application structure posibilities with native-image

[VaginAY]

Hello.

I'm interested in the possibility of organizing the following project structure:

1. Each bundle included in the application exists on its own and is compiled separately using the native-image utility.
2. The head file can pick up these bundles. In this case, bundles can be deleted and added in runtime, but this does not break the work.

In other words, the single image that is now obtained from the results of GraalVM is divided into separate native files (possibly dynamic libraries) in accordance with the original bundle structure.

The current monolithic image, as given in the examples, does not allow updating individual modules, adding or removing them during operation, as far as I understand.