Closed mpumd closed 2 years ago
I guess you are missing some bits but the principle makes sense, and unless I am mistaken that what we will achieve via https://github.com/spring-projects-experimental/spring-native/issues/1247 that is about to be fixed with the upcoming NBT 0.9.13 release. This will be less error prone and much easier to use.
Please check our updated docs and *-agent
samples when Spring Native 0.12.1 will be released, and reopen or comment here if that does not work for your use case.
Hi everyone,
I'm currently test some migrates of business spring boot applications for a company. After 4 weeks, I found a best way to have a satisfactory result with combine the tracing agent of graalvm and the plugin aot of spring native.
configuration :
I use a sequence of two differents maven lifecycle like following :
The tracing agent is activated during a integration test which call all endpoints. Using a real infrastructure seems to be important during the test. For example, use h2 instead of oracle db could causes a runtime fail when you change configuration to target oracle.
If I use only the spring aot plugin, I have the following issue at runtime of the native image packaged inside docker image :
Using the tracing-agent only causes a compilation error on the native build.
So what do you think about my solution ? Thanks.