Enable Section Summary TOC for small pages
This commit is contained in:
Rob Winch
@@ -1,5 +1,6 @@
|
||||
[[webflux-client]]
|
||||
= WebClient
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
Spring WebFlux includes a client to perform HTTP requests with. `WebClient` has a
|
||||
functional, fluent API based on Reactor, see xref:web-reactive.adoc#webflux-reactive-libraries[Reactive Libraries],
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[webflux-client-testing]]
|
||||
= Testing
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
To test code that uses the `WebClient`, you can use a mock web server, such as the
|
||||
https://github.com/square/okhttp#mockwebserver[OkHttp MockWebServer]. To see an example
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
:chapter: webflux
|
||||
[[spring-webflux]]
|
||||
= Spring WebFlux
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
The original web framework included in the Spring Framework, Spring Web MVC, was
|
||||
purpose-built for the Servlet API and Servlet containers. The reactive-stack web framework,
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[webflux-ann-methods]]
|
||||
= Handler Methods
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webmvc/mvc-controller/ann-methods.adoc[See equivalent in the Servlet stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[webflux-ann-typeconversion]]
|
||||
= Type Conversion
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webmvc/mvc-controller/ann-methods/typeconversion.adoc[See equivalent in the Servlet stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[webflux-http2]]
|
||||
= HTTP/2
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webmvc/mvc-http2.adoc[See equivalent in the Servlet stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[webflux-web-security]]
|
||||
= Web Security
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webmvc/mvc-security.adoc[See equivalent in the Servlet stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[webflux-uri-building]]
|
||||
= URI Links
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webmvc/mvc-uri-building.adoc[See equivalent in the Servlet stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[mvc-view]]
|
||||
= View Technologies
|
||||
:page-section-summary-toc: 1
|
||||
[.small]#xref:web/webflux-view.adoc[See equivalent in the Reactive stack]#
|
||||
|
||||
The use of view technologies in Spring MVC is pluggable. Whether you decide to use
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[mvc-view-thymeleaf]]
|
||||
= Thymeleaf
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webflux-view.adoc#webflux-view-thymeleaf[See equivalent in the Reactive stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[mvc-view-xml-marshalling]]
|
||||
= XML Marshalling
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
The `MarshallingView` uses an XML `Marshaller` (defined in the `org.springframework.oxm`
|
||||
package) to render the response content as XML. You can explicitly set the object to be
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
:chapter: mvc
|
||||
[[spring-web-mvc]]
|
||||
= Spring Web MVC
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
Spring Web MVC is the original web framework built on the Servlet API and has been included
|
||||
in the Spring Framework from the very beginning. The formal name, "Spring Web MVC,"
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[mvc-config]]
|
||||
= MVC Config
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webflux/dispatcher-handler.adoc#webflux-framework-config[See equivalent in the Reactive stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[mvc-ann-methods]]
|
||||
= Handler Methods
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webflux/controller/ann-methods.adoc[See equivalent in the Reactive stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[mvc-http2]]
|
||||
= HTTP/2
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webflux/http2.adoc[See equivalent in the Reactive stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[mvc-web-security]]
|
||||
= Web Security
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webflux/security.adoc[See equivalent in the Reactive stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[mvc-servlet-config]]
|
||||
= Web MVC Config
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
[.small]#xref:web/webflux/dispatcher-handler.adoc#webflux-framework-config[See equivalent in the Reactive stack]#
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[websocket]]
|
||||
= WebSockets
|
||||
:page-section-summary-toc: 1
|
||||
[.small]#xref:web/webflux-websocket.adoc[See equivalent in the Reactive stack]#
|
||||
|
||||
This part of the reference documentation covers support for Servlet stack, WebSocket
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[websocket-stomp]]
|
||||
= STOMP
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
The WebSocket protocol defines two types of messages (text and binary), but their
|
||||
content is undefined. The protocol defines a mechanism for client and server to negotiate a
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[websocket-stomp-authorization]]
|
||||
= Authorization
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
Spring Security provides
|
||||
{docs-spring-security}/servlet/integrations/websocket.html#websocket-authorization[WebSocket sub-protocol authorization]
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
[[websocket-stomp-benefits]]
|
||||
= Benefits
|
||||
:page-section-summary-toc: 1
|
||||
|
||||
Using STOMP as a sub-protocol lets the Spring Framework and Spring Security
|
||||
provide a richer programming model versus using raw WebSockets. The same point can be
|
||||
|
||||
Reference in New Issue
Block a user