Storm already ships Spring Boot integration; the 1.13.0 milestone tightens it further. This issue covers AOT processing and GraalVM native images.
Two problems today. Repository beans are registered by a BeanFactoryPostProcessor using instance suppliers, which AOT processing cannot serialize, so a native build loses the repositories. And nothing registers reflection hints for entities, records and repository interfaces. The compile-time type index already knows all of these types, which puts Storm in a better position than runtime-model frameworks: the hints can be generated from the index instead of discovered reflectively at build time.
Tasks:
Storm already ships Spring Boot integration; the 1.13.0 milestone tightens it further. This issue covers AOT processing and GraalVM native images.
Two problems today. Repository beans are registered by a
BeanFactoryPostProcessorusing instance suppliers, which AOT processing cannot serialize, so a native build loses the repositories. And nothing registers reflection hints for entities, records and repository interfaces. The compile-time type index already knows all of these types, which puts Storm in a better position than runtime-model frameworks: the hints can be generated from the index instead of discovered reflectively at build time.Tasks:
RuntimeHintsRegistrarfed by the compile-time type index