GraalVM Native Image compatibility

[shomub]

Type: Feature

Is your feature request related to a problem? Please describe.
spring-cloud-aws support for spring-boot 3 running on spring native. See attached reproducer to see issue on running the bootBuildImage Task

Describe the solution you'd like
spring-clould-aws support for spring boot 3 on spring native

[maciejwalkowiak]

@shomub i think you missed the attachment

[shomub]

complete.zip
uploaded file

[maciejwalkowiak]

Version 2.x will not be compatible with Spring Native. 3.0 on the other hand will since it is using GraalVM ready AWS SDK v2. I will take a look what's the current state of native support for 3.x codebase.

[shomub]

Thank you Maciej!

…

On Wed, Jul 27, 2022, 10:52 AM Maciej Walkowiak ***@***.***> wrote: Version 2.x will not be compatible with Spring Native. 3.0 on the other hand will since it is using GraalVM ready AWS SDK v2. I will take a look what's the current state of native support for 3.x codebase. — Reply to this email directly, view it on GitHub <#468 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIANQTI5SVZI44VJRKRU2ZDVWFELNANCNFSM54ZR6NJA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[maciejwalkowiak]

DynamoDB Enhanced Client BeanTableSchema is not compatible with GraalVM Native Image (aws/aws-sdk-java-v2#2445). Either this issue has to be fixed, or we need to advice users to use StaticTableSchema in docs for building native images.

[davidmelia]

Hi, related to this I noticed the AWS parameter store integration (3.0.0-M3) is stripped out when doing a native build such that it is invoked during the native build step but then never invoked when running that executable. This should work similar to the spring cloud config client.

[jamesforward999]

I've also noticed my @SqsListener methods not being set up properly as well when running via GraalVM on a Spring Boot 3.0/AOT app. Can tell this as apparently the SqsListener isn't registered when I look up the DefaultContainerRegistry - apparently no listeners exist. Is this known about?

[tomazfernandes]

I've also noticed my @SqsListener methods not being set up properly as well when running via GraalVM on a Spring Boot 3.0/AOT app. Can tell this as apparently the SqsListener isn't registered when I look up the DefaultContainerRegistry - apparently no listeners exist. Is this known about?

I haven't had the chance to look into native yet, so I can't tell exactly what's going on.

What we do in SQS is we look for the @SqsListener annotations on the beans here. I'd guess this introspection method we use isn't supported OOTB.

Looking at the Spring Kafka project which uses a similar approach, I see they have this hints file, so we will probably need something similar.

[jamesforward999]

I've also noticed my @SqsListener methods not being set up properly as well when running via GraalVM on a Spring Boot 3.0/AOT app. Can tell this as apparently the SqsListener isn't registered when I look up the DefaultContainerRegistry - apparently no listeners exist. Is this known about?

I haven't had the chance to look into native yet, so I can't tell exactly what's going on.

What we do in SQS is we look for the @SqsListener annotations on the beans here. I'd guess this introspection method we use isn't supported OOTB.

Looking at the Spring Kafka project which uses a similar approach, I see they have this hints file, so we will probably need something similar.

I was actually just playing around with this and I got it to work (in a horribly hacky way) by adding into my reflect-config.json file all the classes that the native-image-agent picked up under the io.awspring package (and setting them to have full reflection capability), eg:

    "name": "io.awspring.cloud.sqs.annotation.SqsListener",
    "allDeclaredConstructors": true,
    "allPublicConstructors": true,
    "allDeclaredFields": true,
    "allPublicFields": true,
    "allDeclaredMethods": true,
    "allPublicMethods": true
  }

This could probably be far more granular on a class-by-class basis, but this worked for me (I also added equivalent entries for my own project's classes)