You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 23, 2023. It is now read-only.
* The `IntegrationFlow` interface can be proxied at runtime
* The resource pattern for JDBC schemas should really be a regex pattern
* The HTTP and WebFlux request mappings need a reflection access to
method of their handlers to map
* Process interfaces with a `@MessagingGateway` and register their
proxy hints
* Improve `IntegrationApplication` in the sample to cover the mentioned
above cases about an `IntegrationFlow` proxy and `@MessagingGateway`
* Fix `ControlBusGateway` to emit really a Control Bus command
* Use `WebClient.Builder` bean from the ctx for application logic
* Add reflection info for `AbstractEndpoint` to satisfy Control Bus requirements
* Add some common types to satisfy common SpEL expressions
* Add explicit `@TypeHint` for `Message` impls -
* Add more Spring Integration types specific to `MessageStore` serialization functionality
* Add programmatic scan for `IntegrationNode` impls instead of huge number of
explicit types in `@TypeHint`
* Add `JdbcChannelMessageStore` logic into the sample to cover its serialization functionality
* Add `@SerializationHint` for messaging types
* Add programmatic scan for `IntegrationNode` impls instead of huge number of
explicit types in `@TypeHint`
* Add `JdbcChannelMessageStore` logic into the sample to cover its serialization functionality
* Add `RedisChannelMessageStore` logic into the sample to cover JSON (un)marshaling feature
* Rely on Spring Integration version from parent in the sample
Closesgh-894
0 commit comments