Browse Source

Add Migration Steps for Messaging

Closes gh-17509
pull/17520/head
Josh Cummings 5 months ago
parent
commit
4b15b2b94e
No known key found for this signature in database
GPG Key ID: 869B37A20E876129
  1. 40
      docs/modules/ROOT/pages/migration-7/messaging.adoc

40
docs/modules/ROOT/pages/migration-7/messaging.adoc

@ -0,0 +1,40 @@ @@ -0,0 +1,40 @@
== Messaging Migrations
[[use-path-pattern]]
== Use PathPatternMessageMatcher by Default
In Spring Security 7, `SimpDestMessageMatcher` is no longer supported and will use `PathPatternMessageMatcher` by default.
To check how prepared you are for this change, you can publish this bean:
[tabs]
======
Java::
+
[source,java,role="primary"]
----
@Bean
PathPatternMessageMatcherBuilderFactoryBean messageMatcherBuilder() {
return new PathPatternMessageMatcherBuilderFactoryBean();
}
----
Kotlin::
+
[source,kotlin,role="secondary"]
----
@Bean
fun messageMatcherBuilder(): PathPatternMessageMatcherBuilderFactoryBean {
return PathPatternMessageMatcherBuilderFactoryBean()
}
----
Xml::
+
[source,xml,role="secondary"]
----
<b:bean class="org.springframework.security.config.web.messaging.PathPatternMessageMatcherBuilderFactoryBean"/>
----
======
This will tell the Spring Security DSL to use `PathPatternMessageMatcher` for all message matchers that it constructs.
Loading…
Cancel
Save