The libraries are currently using reflection in 4 different places (if I'm not missing something):

• ApiClientBuilder - abstractions
• RequestInformation - abstractions
• KiotaSerialization - abstractions
• JsonSerializationWriter - serialization/json

As ppl can roll their json serialization support I'm not concerned with the latter.
But, the usage of reflection in abstractions means that this is not going to run without configuration when compiled with native-image, especially for the usage in Quarkus applications.

Since we are in control of the generator, I do believe that we can find solutions to completely avoid the usage of reflection in the abstractions layer.