diff --git a/spring-cloud-stream/3.0.3.RELEASE/reference/html/spring-cloud-stream.html b/spring-cloud-stream/3.0.3.RELEASE/reference/html/spring-cloud-stream.html index cf26f7c3..f8ced786 100644 --- a/spring-cloud-stream/3.0.3.RELEASE/reference/html/spring-cloud-stream.html +++ b/spring-cloud-stream/3.0.3.RELEASE/reference/html/spring-cloud-stream.html @@ -158,7 +158,7 @@ $(addBlockSwitches);
  • Foreign event-driven sources
  • @@ -1417,10 +1417,10 @@ source of the data may be a classic REST endpoint. How do we bridge such source

    Here, for both samples we’ll use a standard MVC endpoint method called delegateToSupplier bound to the root web context, delegating incoming requests to stream via two different mechanisms - -imperative (via StreamBridgeUtils) and reactive (via EmitterProcessor).

    +imperative (via StreamBridge) and reactive (via EmitterProcessor).

    -
    Using StreamBridgeUtils
    +
    Using StreamBridge
    @SpringBootApplication
    @@ -1432,7 +1432,7 @@ public class WebSourceApplication {
     	}
     
     	@Autowired
    -	private StreamBridgeUtils streamBridge;
    +	private StreamBridge streamBridge;
     
     	@RequestMapping
     	@ResponseStatus(HttpStatus.ACCEPTED)
    @@ -1444,7 +1444,7 @@ public class WebSourceApplication {
     
    -

    Here we autowire a StreamBridgeUtils bean which allows us to send data to an output binding effectively +

    Here we autowire a StreamBridge bean which allows us to send data to an output binding effectively bridging non-stream application with spring-cloud-stream. Note that preceding example does not have any source functions defined (e.g., Supplier bean) leaving the framework with no trigger to create source bindings, which would be typical for cases where configuration contains function beans. @@ -4796,4 +4796,4 @@ The steps are also highlighted in the - \ No newline at end of file +