-
Notifications
You must be signed in to change notification settings - Fork 38.8k
Description
zyro opened SPR-11771 and commented
when we got a scenario like this:
DispatcherServletservlet-mappinglike\*.doand/stomp/\*- stomp endpoint registration on
/stomp
the requests will not match because AbstractHandlerMapping.alwaysUseFullPath is false by default and so e.g. a request to /stomp/info will lead to a lookup-path of /info which does not match the sockJS handler-mapping, that gets a pattern of /stomp/**
dirty workaround for me was applicationContext.getBean("stompWebSocketHandlerMapping").setAlwaysUseFullPath(true) when the context is fully loaded.
would be cool to get a chance to configure the handlerMapping itself, or at least the alwaysUseFullPath flag using AbstractWebSocketMessageBrokerConfigurer, without needing to fall back to WebSocketMessageBrokerConfigurationSupport overrding the whole handlerMapping bean.
maybe relevant for webSocketHandlerMapping as well?
Affects: 4.0.4
Issue Links:
- Configuration of path mapping options for websockets via XML [SPR-12621] #17222 Configuration of path mapping options for websockets via XML
1 votes, 3 watchers