README.adoc 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268
  1. :spring_version: current
  2. :jackson: https://wiki.fasterxml.com/JacksonHome
  3. :AtMessageMapping: https://docs.spring.io/spring/docs/{spring_version}/javadoc-api/org/springframework/messaging/handler/annotation/MessageMapping.html
  4. :AtController: https://docs.spring.io/spring/docs/{spring_version}/javadoc-api/org/springframework/stereotype/Controller.html
  5. :AtEnableWebSocketMessageBroker: https://docs.spring.io/spring/docs/{spring_version}/javadoc-api/org/springframework/messaging/simp/config/EnableWebSocketMessageBroker.html
  6. :Stomp_JS: http://jmesnil.net/stomp-websocket/doc/
  7. :AtSendTo: https://docs.spring.io/spring/docs/{spring_version}/javadoc-api/org/springframework/messaging/handler/annotation/SendTo.html
  8. :toc:
  9. :icons: font
  10. :source-highlighter: prettify
  11. :project_id: gs-messaging-stomp-websocket
  12. This guide walks you through the process of creating a "`Hello, world`" application that
  13. sends messages back and forth between a browser and a server. WebSocket is a thin,
  14. lightweight layer above TCP. This makes it suitable for using "`subprotocols`" to embed
  15. messages. In this guide, we use
  16. http://en.wikipedia.org/wiki/Streaming_Text_Oriented_Messaging_Protocol[STOMP] messaging
  17. with Spring to create an interactive web application. STOMP is a subprotocol operating
  18. on top of the lower-level WebSocket.
  19. == What You Will build
  20. You will build a server that accepts a message that carries a user's name. In response,
  21. the server will push a greeting into a queue to which the client is subscribed.
  22. == What You Need
  23. include::https://raw.githubusercontent.com/spring-guides/getting-started-macros/main/prereq_editor_jdk_buildtools.adoc[]
  24. include::https://raw.githubusercontent.com/spring-guides/getting-started-macros/main/how_to_complete_this_guide.adoc[]
  25. [[scratch]]
  26. == Starting with Spring Initializr
  27. You can use this https://start.spring.io/#!type=maven-project&groupId=com.example&artifactId=messaging-stomp-websocket&name=messaging-stomp-websocket&description=Demo%20project%20for%20Spring%20Boot&packageName=com.example.messaging-stomp-websocket&dependencies=websocket[pre-initialized project] and click Generate to download a ZIP file. This project is configured to fit the examples in this tutorial.
  28. To manually initialize the project:
  29. . Navigate to https://start.spring.io.
  30. This service pulls in all the dependencies you need for an application and does most of the setup for you.
  31. . Choose either Gradle or Maven and the language you want to use. This guide assumes that you chose Java.
  32. . Click *Dependencies* and select *Websocket*.
  33. . Click *Generate*.
  34. . Download the resulting ZIP file, which is an archive of a web application that is configured with your choices.
  35. NOTE: If your IDE has the Spring Initializr integration, you can complete this process from your IDE.
  36. NOTE: You can also fork the project from Github and open it in your IDE or other editor.
  37. [[initial]]
  38. == Create a Resource Representation Class
  39. Now that you have set up the project and build system, you can create your STOMP message
  40. service.
  41. Begin the process by thinking about service interactions.
  42. The service will accept messages that contain a name in a STOMP message whose body is a
  43. JSON object. If the name is `Fred`, the message might resemble the following:
  44. ====
  45. [source,json]
  46. ----
  47. {
  48. "name": "Fred"
  49. }
  50. ----
  51. ====
  52. To model the message that carries the name, you can create a plain old Java object with a
  53. `name` property and a corresponding `getName()` method, as the following listing (from
  54. `src/main/java/com/example/messagingstompwebsocket/HelloMessage.java`) shows:
  55. ====
  56. [source,java,tabsize=2]
  57. ----
  58. include::complete/src/main/java/com/example/messagingstompwebsocket/HelloMessage.java[]
  59. ----
  60. ====
  61. Upon receiving the message and extracting the name, the service will process it by
  62. creating a greeting and publishing that greeting on a separate queue to which the client
  63. is subscribed. The greeting will also be a JSON object, which as the following listing
  64. shows:
  65. ====
  66. [source,json]
  67. ----
  68. {
  69. "content": "Hello, Fred!"
  70. }
  71. ----
  72. ====
  73. To model the greeting representation, add another plain old Java object with a `content`
  74. property and a corresponding `getContent()` method, as the following listing (from
  75. `src/main/java/com/example/messagingstompwebsocket/Greeting.java`) shows:
  76. ====
  77. [source,java,tabsize=2]
  78. ----
  79. include::complete/src/main/java/com/example/messagingstompwebsocket/Greeting.java[]
  80. ----
  81. ====
  82. Spring will use the {jackson}[Jackson JSON] library to automatically marshal instances of
  83. type `Greeting` into JSON.
  84. Next, you will create a controller to receive the hello message and send a greeting
  85. message.
  86. == Create a Message-handling Controller
  87. In Spring's approach to working with STOMP messaging, STOMP messages can be routed to
  88. {AtController}[`@Controller`] classes. For example, the `GreetingController` (from
  89. `src/main/java/com/example/messagingstompwebsocket/GreetingController.java`) is mapped to
  90. handle messages to the `/hello` destination, as the following listing shows:
  91. ====
  92. [source,java,tabsize=2]
  93. ----
  94. include::complete/src/main/java/com/example/messagingstompwebsocket/GreetingController.java[]
  95. ----
  96. ====
  97. This controller is concise and simple, but plenty is going on. We break it down step by
  98. step.
  99. The {AtMessageMapping}[`@MessageMapping`] annotation ensures that, if a message is sent to
  100. the `/hello` destination, the `greeting()` method is called.
  101. The payload of the message is bound to a `HelloMessage` object, which is passed into
  102. `greeting()`.
  103. Internally, the implementation of the method simulates a processing delay by causing the
  104. thread to sleep for one second. This is to demonstrate that, after the client sends a
  105. message, the server can take as long as it needs to asynchronously process the message.
  106. The client can continue with whatever work it needs to do without waiting for the
  107. response.
  108. After the one-second delay, the `greeting()` method creates a `Greeting` object and
  109. returns it. The return value is broadcast to all subscribers of `/topic/greetings`, as
  110. specified in the {AtSendTo}[`@SendTo`] annotation. Note that the name from the input
  111. message is sanitized, since, in this case, it will be echoed back and re-rendered in the
  112. browser DOM on the client side.
  113. == Configure Spring for STOMP messaging
  114. Now that the essential components of the service are created, you can configure Spring to
  115. enable WebSocket and STOMP messaging.
  116. Create a Java class named `WebSocketConfig` that resembles the following listing (from
  117. `src/main/java/com/example/messagingstompwebsocket/WebSocketConfig.java`):
  118. ====
  119. [source,java,tabsize=2]
  120. ----
  121. include::complete/src/main/java/com/example/messagingstompwebsocket/WebSocketConfig.java[]
  122. ----
  123. ====
  124. `WebSocketConfig` is annotated with `@Configuration` to indicate that it is a Spring
  125. configuration class. It is also annotated with
  126. {AtEnableWebSocketMessageBroker}[`@EnableWebSocketMessageBroker`]. As its name suggests,
  127. `@EnableWebSocketMessageBroker` enables WebSocket message handling, backed by a message
  128. broker.
  129. The `configureMessageBroker()` method implements the default method in
  130. `WebSocketMessageBrokerConfigurer` to configure the message broker. It starts by calling
  131. `enableSimpleBroker()` to enable a simple memory-based message broker to carry the
  132. greeting messages back to the client on destinations prefixed with `/topic`. It also
  133. designates the `/app` prefix for messages that are bound for methods annotated with
  134. `@MessageMapping`. This prefix will be used to define all the message mappings. For
  135. example, `/app/hello` is the endpoint that the `GreetingController.greeting()` method is
  136. mapped to handle.
  137. The `registerStompEndpoints()` method registers the `/gs-guide-websocket` endpoint for websocket connections.
  138. == Create a Browser Client
  139. With the server-side pieces in place, you can turn your attention to the JavaScript client
  140. that will send messages to and receive messages from the server side.
  141. Create an `index.html` file similar to the following listing (from
  142. `src/main/resources/static/index.html`):
  143. ====
  144. [source,html]
  145. ----
  146. include::complete/src/main/resources/static/index.html[]
  147. ----
  148. ====
  149. This HTML file imports the https://stomp-js.github.io/[`StompJS`] javascript library that will be used to
  150. communicate with our server through STOMP over websocket. We also import `app.js`, which
  151. contains the logic of our client application. The following listing (from
  152. `src/main/resources/static/app.js`) shows that file:
  153. ====
  154. [source,javascript,tabsize=2]
  155. ----
  156. include::complete/src/main/resources/static/app.js[]
  157. ----
  158. ====
  159. The main pieces of this JavaScript file to understand are the `stompClient.onConnect` and `sendName`
  160. functions.
  161. `stompClient` is initialized with `brokerURL` referring to path `/gs-guide-websocket`,
  162. which is where our websockets server waits for
  163. connections. Upon a successful connection, the client subscribes to the `/topic/greetings`
  164. destination, where the server will publish greeting messages. When a greeting is received
  165. on that destination, it will append a paragraph element to the DOM to display the greeting
  166. message.
  167. The `sendName()` function retrieves the name entered by the user and uses the STOMP client
  168. to send it to the `/app/hello` destination (where `GreetingController.greeting()` will
  169. receive it).
  170. The `main.css` can be omitted if you like, or you can create an empty
  171. one, just so the `<link>` can be resolved.
  172. == Make the Application Executable
  173. Spring Boot creates an application class for you. In this case, it needs no further
  174. modification. You can use it to run this application. The following listing (from
  175. `src/main/java/com/example/messagingstompwebsocket/MessagingStompWebsocketApplication.java`)
  176. shows the application class:
  177. ====
  178. [source,java,tabsize=2]
  179. ----
  180. include::complete/src/main/java/com/example/messagingstompwebsocket/MessagingStompWebsocketApplication.java[]
  181. ----
  182. ====
  183. include::https://raw.githubusercontent.com/spring-guides/getting-started-macros/main/spring-boot-application-new-path.adoc[]
  184. include::https://raw.githubusercontent.com/spring-guides/getting-started-macros/main/build_an_executable_jar_subhead.adoc[]
  185. include::https://raw.githubusercontent.com/spring-guides/getting-started-macros/main/build_an_executable_jar_with_both.adoc[]
  186. Logging output is displayed. The service should be up and running within a few seconds.
  187. == Test the service
  188. Now that the service is running, point your browser at http://localhost:8080 and click the *Connect* button.
  189. Upon opening a connection, you are asked for your name. Enter your name and click *Send*.
  190. Your name is sent to the server as a JSON message over STOMP. After a one-second simulated
  191. delay, the server sends a message back with a "`Hello`" greeting that is displayed on the
  192. page. At this point, you can send another name or you can click the *Disconnect* button to
  193. close the connection.
  194. == Summary
  195. Congratulations! You have just developed a STOMP-based messaging service with Spring.
  196. == See Also
  197. The following guides may also be helpful:
  198. * https://stomp-js.github.io/[StompJS client library docs]
  199. * https://spring.io/guides/gs/serving-web-content/[Serving Web Content with Spring MVC]
  200. * https://spring.io/guides/gs/spring-boot/[Building an Application with Spring Boot]
  201. include::https://raw.githubusercontent.com/spring-guides/getting-started-macros/main/footer.adoc[]