Skip to content

Move IntegrationFlows factory content into the IntegrationFlow interface with the same reason and deprecate it #3623

Closed
@artembilan

Description

@artembilan

Expected Behavior

Since IntegrationFlow is an interface nothing stops us to have static methods in it.
The better end-user experience would be just to have imported an IntegrationFlow interface and go with fluent API from there an our @Bean definitions.

Current Behavior

We have to know about an IntegrationFlows factory and don't forget to import it into our code.

Context

It is a little burden do not forget to import an IntegrationFlows factory to get access to from(...) API.
Better to let to end-users to deal only with an IntegrationFlow interface as return type on a @Bean definition, as well as in the bean definition code.
Similar API exposure exits in the WebClient from WebFlux.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions