GitHub-Spring
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Warn against direct usage of Servlet API in WebFlux apps 

Closes gh-28872
pull/30915/head
Brian Clozel 2 years ago
parent
826776f321
commit
df22ba39f8
1 changed files with 3 additions and 0 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 3
      framework-docs/modules/ROOT/pages/web/webflux/new-framework.adoc

3
framework-docs/modules/ROOT/pages/web/webflux/new-framework.adoc
Unescape View File

@ -189,6 +189,9 @@ lets applications use the Servlet API directly if they need to. Spring WebFlux
relies on Servlet non-blocking I/O and uses the Servlet API behind a low-level relies on Servlet non-blocking I/O and uses the Servlet API behind a low-level
adapter. It is not exposed for direct use. adapter. It is not exposed for direct use.
NOTE: It is strongly advised not to map Servlet filters nor directly manipulate the Servlet API in the context of a WebFlux application.
For the reasons listed above, mixing blocking I/O and non-blocking I/O in the same context will cause runtime issues.
For Undertow, Spring WebFlux uses Undertow APIs directly without the Servlet API. For Undertow, Spring WebFlux uses Undertow APIs directly without the Servlet API.

Write Preview
Loading…
Cancel
Save