Fix image::image
This commit is contained in:
@@ -140,7 +140,7 @@ continuity and consistency with each other, they are available side by side, and
|
||||
from each side benefits both sides. The following diagram shows how the two relate, what they
|
||||
have in common, and what each supports uniquely:
|
||||
|
||||
image::images/spring-mvc-and-webflux-venn.png[]
|
||||
image::spring-mvc-and-webflux-venn.png[]
|
||||
|
||||
We suggest that you consider the following specific points:
|
||||
|
||||
|
||||
@@ -154,7 +154,7 @@ are effectively inherited and can be overridden (that is, re-declared) in the Se
|
||||
child `WebApplicationContext`, which typically contains beans local to the given `Servlet`.
|
||||
The following image shows this relationship:
|
||||
|
||||
image::images/mvc-context-hierarchy.png[]
|
||||
image::mvc-context-hierarchy.png[]
|
||||
|
||||
The following example configures a `WebApplicationContext` hierarchy:
|
||||
|
||||
|
||||
@@ -1114,7 +1114,7 @@ Both the Java configuration (that is, `@EnableWebSocketMessageBroker`) and the X
|
||||
workflow. The following diagram shows the components used when the simple built-in message
|
||||
broker is enabled:
|
||||
|
||||
image::images/message-flow-simple-broker.png[]
|
||||
image::message-flow-simple-broker.png[]
|
||||
|
||||
The preceding diagram shows three message channels:
|
||||
|
||||
@@ -1126,7 +1126,7 @@ server-side application code.
|
||||
The next diagram shows the components used when an external broker (such as RabbitMQ)
|
||||
is configured for managing subscriptions and broadcasting messages:
|
||||
|
||||
image::images/message-flow-broker-relay.png[]
|
||||
image::message-flow-broker-relay.png[]
|
||||
|
||||
The main difference between the two preceding diagrams is the use of the "`broker relay`" for passing
|
||||
messages up to the external STOMP broker over TCP and for passing messages down from the
|
||||
|
||||
Reference in New Issue
Block a user