Empty asyncapi.* documents when running native executable

[brianbuchanan]

Tried this with Quarkus 3.2.6.Final and 3.6.7.

When I compile a native executable and create a docker image and run it and go to http://localhost:8080/asyncapi.json, I get an empty document "{}".

This is not the case when I compile a JVM exe and hit the asyncapi.json endpoint. It returns the beautiful document I expect to see.

Verified that when the app starts, I see:

2024-01-31 15:48:13,340 INFO [io.qua.asy.ann.sca.AsyncApiRecorder] (main) AsycnApiRecorder.store to /tmp/asyncApi.yaml
2024-01-31 15:48:13,341 INFO [io.qua.asy.ann.sca.AsyncApiRecorder] (main) AsycnApiRecorder.store to /tmp/asyncApi.json
2024-01-31 15:48:13,341 INFO [io.qua.asy.ann.sca.AsyncApiRecorder] (main) AsycnApiRecorder.store to /tmp/asyncApi.puml

And the files exist in the container, but they contain a blank body.

I don't know enough about how the asyncapi docs are generated and if there is a trick to getting this to work with a native executable. Wanted to reach out for help to see if I am missing something.

This is my first time submitting an issue, so if I have left out standard information that is needed to help debug this issue, please let me know. This extension is very powerful and I appreciate the contribution to the community. Thanks.

[ChMThiel]

The extension was not implemented for native execution and therefore that was not tested.
Right now i have no need for native execution and no time to dive in to the problem - I'm sorry.
But if you want to go into it - fell free to submit a PR.