-
Notifications
You must be signed in to change notification settings - Fork 612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generalize binding outside message channels #519
Milestone
Comments
This was referenced Sep 27, 2016
mbogoevici
added a commit
to mbogoevici/spring-cloud-stream
that referenced
this issue
Dec 1, 2016
Fixes spring-cloud#519 Introduces some internal changes to the framework allowing the use of other types than MessageChannel/SubscribableChannel as bindable types (e.g. Flux, Observable, KStream, etc.) - Modify BinderFactory to allow the retrieval and lookup of a binder not only by name, but also by BoundElement type - Subsequent changes to ChannelBindingService and tests to account for the modified signature - Introduce BoundElementFactory as the contract for creating bound elements
mbogoevici
added a commit
to mbogoevici/spring-cloud-stream
that referenced
this issue
Dec 1, 2016
Fixes spring-cloud#519 Introduces some internal changes to the framework allowing the use of other types than MessageChannel/SubscribableChannel as bindable types (e.g. Flux, Observable, KStream, etc.) - Modify BinderFactory to allow the retrieval and lookup of a binder not only by name, but also by BoundElement type - Subsequent changes to ChannelBindingService and tests to account for the modified signature - Introduce BoundElementFactory as the contract for creating bound elements
mbogoevici
added a commit
to mbogoevici/spring-cloud-stream
that referenced
this issue
Dec 7, 2016
Fixes spring-cloud#519 Introduces some internal changes to the framework allowing the use of other types than MessageChannel/SubscribableChannel as bindable types (e.g. Flux, Observable, KStream, etc.) - Modify BinderFactory to allow the retrieval and lookup of a binder not only by name, but also by BoundElement type - Subsequent changes to ChannelBindingService and tests to account for the modified signature - Introduce BoundElementFactory as the contract for creating bound elements Renamed BoundElementFactory to BindableTargetFactory and ChannelBindingService to BindingService Signed-off-by: Marius Bogoevici <mbogoevici@pivotal.io> Fix imports Signed-off-by: Marius Bogoevici <mbogoevici@pivotal.io> Renamed along with ChannelBindingService Signed-off-by: Marius Bogoevici <mbogoevici@pivotal.io> Addressing PR comments Addressed a couple of comments missed in the previous pass Renaming all 'channel'
mbogoevici
added a commit
to mbogoevici/spring-cloud-stream
that referenced
this issue
Dec 11, 2016
Fixes spring-cloud#519 Introduces some internal changes to the framework allowing the use of other types than MessageChannel/SubscribableChannel as bindable types (e.g. Flux, Observable, KStream, etc.) - Modify BinderFactory to allow the retrieval and lookup of a binder not only by name, but also by BoundElement type - Subsequent changes to ChannelBindingService and tests to account for the modified signature - Introduce BoundElementFactory as the contract for creating bound elements Renamed BoundElementFactory to BindableTargetFactory and ChannelBindingService to BindingService Signed-off-by: Marius Bogoevici <mbogoevici@pivotal.io> Fix imports Signed-off-by: Marius Bogoevici <mbogoevici@pivotal.io> Renamed along with ChannelBindingService Signed-off-by: Marius Bogoevici <mbogoevici@pivotal.io> Addressing PR comments Addressed a couple of comments missed in the previous pass Renaming all 'channel' Signed-off-by: Marius Bogoevici <mbogoevici@pivotal.io>
mbogoevici
added a commit
to mbogoevici/spring-cloud-stream
that referenced
this issue
Dec 12, 2016
Fixes spring-cloud#519 Introduces some internal changes to the framework allowing the use of other types than MessageChannel/SubscribableChannel as bindable types (e.g. Flux, Observable, KStream, etc.) - Modify BinderFactory to allow the retrieval and lookup of a binder not only by name, but also by binding target type - Subsequent changes to ChannelBindingService and tests to account for the modified signature - Introduce BindingTargetFactory as the contract for creating bound elements - Remove any references to chanels and bound elements and use 'binding target' systematically across the board
mbogoevici
added a commit
to mbogoevici/spring-cloud-stream
that referenced
this issue
Dec 12, 2016
Fixes spring-cloud#519 Introduces some internal changes to the framework allowing the use of other types than MessageChannel/SubscribableChannel as bindable types (e.g. Flux, Observable, KStream, etc.) - Modify BinderFactory to allow the retrieval and lookup of a binder not only by name, but also by binding target type - Subsequent changes to ChannelBindingService and tests to account for the modified signature - Introduce BindingTargetFactory as the contract for creating bound elements - Remove any references to chanels and bound elements and use 'binding target' systematically across the board
mbogoevici
added a commit
to mbogoevici/spring-cloud-stream
that referenced
this issue
Dec 12, 2016
Fixes spring-cloud#519 Introduces some internal changes to the framework allowing the use of other types than MessageChannel/SubscribableChannel as bindable types (e.g. Flux, Observable, KStream, etc.) - Modify BinderFactory to allow the retrieval and lookup of a binder not only by name, but also by binding target type - Subsequent changes to ChannelBindingService and tests to account for the modified signature - Introduce BindingTargetFactory as the contract for creating bound elements - Remove any references to chanels and bound elements and use 'binding target' systematically across the board
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a developer, I'd like to generalize binding mechanism outside of the message channels, so it is generic enough for all types of applications and not messaging based.
The text was updated successfully, but these errors were encountered: