-
Notifications
You must be signed in to change notification settings - Fork 353
Restore Spring Integration support #1134
Comments
Fixes spring-attic#1155 Related to spring-attic#1134 The `FactoryBean.OBJECT_TYPE_ATTRIBUTE` is crucial for those `FactoryBean` impls which does not expose the target type during compilation. * Add `FactoryBean.OBJECT_TYPE_ATTRIBUTE` as a candidate for the `DefaultBeanRegistrationWriter.getAttributeFilter()` since that one is `false` by default anyway * Rework `IntegrationApplication` to reflect the current Spring Boot state * Use `spring-integration-5.5.6-SNAPSHOT` for the latest bean definition changes over there The `build.sh -a` now passes for the integration sample. Cannot confirm in the native mode since GraalVM doesn't work well on Windows: too long command line. Need to build classpath file (jar with respective META-INF) somehow...
Fixes spring-attic#1155 Related to spring-attic#1134 The `FactoryBean.OBJECT_TYPE_ATTRIBUTE` is crucial for those `FactoryBean` impls which does not expose the target type during compilation. * Add `FactoryBean.OBJECT_TYPE_ATTRIBUTE` as a candidate for the `DefaultBeanRegistrationWriter.getAttributeFilter()` since that one is `false` by default anyway * Rework `IntegrationApplication` to reflect the current Spring Boot state * Use `spring-integration-5.5.6-SNAPSHOT` for the latest bean definition changes over there The `build.sh -a` now passes for the integration sample. Cannot confirm in the native mode since GraalVM doesn't work well on Windows: too long command line. Need to build classpath file (jar with respective META-INF) somehow...
We've made quite a lot of progress. The integration sample now starts in AOT mode but is failing on Native because some annotation hints are missing.
Artem said he'd be following up. @artembilan let me know if I can help. |
Awesome, thanks a lot @snicoll. |
I am moving this one to 0.11.0 in order to allow us to focus on testing which is the highest priority. |
Spring Integration used to work on AOT and now doesn't anymore so I think we need to make sure we fix that first by not changing things in Spring Integration (or fixing them if they have to be). The sample fails currently with:
|
Running the integration samples now leads to:
I suspect that something has been called at build time and is called again at runtime and attempt to register a bean that's already there. @artembilan do you have some cycles to resume this? I intend to spend a bit of time next week on this so any insight would be much appreciated. |
Fixes spring-attic#1134 * Upgrade sample to the latest Spring Integration `5.5.7-SNAPSHOT` * Add `maven-shade-plugin` and `native-maven-plugin` under Windows profile to make native image build working on Windows. Se more info in Native Build Tools docs: https://graalvm.github.io/native-build-tools/latest/maven-plugin.html#long_classpath_and_shading_support This profile simply can go to the `../maven-parent/pom.xml` to make all the samples working on Windows. Or you can remove this on merge since it might be just a noise for a broader community * Add custom `ReactorClientHttpConnector` bean into the sample app, since by default a DNS resolver fails with NPE on Windows in native image. See more info in the: spring-projects/spring-framework#27749 * Add more type nints into the `IntegrationHints`
Require at least Spring Integration |
* Upgrade sample to the latest Spring Integration `5.5.7-SNAPSHOT` * Add more type hints into the `IntegrationHints` See gh-1134
Technically this would work for anyone using |
We could but I thought it would be better to keep it open until we remove the version override in order to have it mentioned in the changelog when effectively supported out of the box (I guess you meant 0.11.0). |
Yes sorry I meant |
To be discussed with @artembilan and @snicoll.
The text was updated successfully, but these errors were encountered: