Although Ant-style, slash-separated, path patterns should feel familiar to web
developers, in message brokers and in messaging it is common to use "." as the
separator, for example in the names of destinations such as topics, queues,
exchanges, etc.
Applications can switch to using "." (dot) instead of "/" (slash) as the separator
for destinations mapped to `@MessageMapping` methods simply by configuring an `AntPathMatcher`
with a customized path separator property. This can be done easily through
the provided Java config and XML namespace.
Applications can switch to using other path separator like "." (dot) instead of
"/" (slash) as the separator for destinations mapped to `@MessageMapping`.
For further details, see <<websocket-stomp-destination-separator>>.
====
The following method arguments are supported for `@MessageMapping` methods:
@ -38267,15 +38261,9 @@ to Ant-style destination patterns.
@@ -38267,15 +38261,9 @@ to Ant-style destination patterns.
[NOTE]
====
Although Ant-style, slash-separated, path patterns should feel familiar to web
developers, in message brokers and in messaging it is common to use "." as the
separator, for example in the names of destinations such as topics, queues,
exchanges, etc.
Applications can switch to using "." (dot) instead of "/" (slash) as the separator
for destinations handled by the broker simply by configuring an `AntPathMatcher`
with a customized path separator property. This can be done easily through
the provided Java config and XML namespace.
Applications can switch to using other path separator like "." (dot) instead of
"/" (slash) as the separator for destinations mapped to `@MessageMapping`.
For further details, see <<websocket-stomp-destination-separator>>.
====
@ -38407,6 +38395,107 @@ and may be useful for example in a cloud environment where the actual host to wh
@@ -38407,6 +38395,107 @@ and may be useful for example in a cloud environment where the actual host to wh
the TCP connection is established is different from the host providing the
cloud-based STOMP service.
[[websocket-stomp-destination-separator]]
==== Destination separator
Although Ant-style, slash-separated, path patterns should feel familiar to web developers,
in message brokers and in messaging it is common to use "." as the separator, for example
in the names of destinations such as topics, queues, exchanges, etc.
Applications can switch to using "." (dot) instead of "/" (slash) as the separator for
destinations handled by the broker simply by configuring an AntPathMatcher with a customized
path separator property. This can be done easily through the provided Java config and XML
namespace.
Below is example configuration that enables using "." separator:
[source,java,indent=0]
[subs="verbatim,quotes"]
----
@Configuration
@EnableWebSocketMessageBroker
public class WebsocketConfig extends AbstractWebSocketMessageBrokerConfigurer {
@Override
public void registerStompEndpoints(StompEndpointRegistry registry) {
registry.addEndpoint("/stomp");
}
@Override
public void configureMessageBroker(MessageBrokerRegistry registry) {