spring-projects / spring-projects/spring-session
Provide alternative to AbstractSessionWebSocketMessageBrokerConfigurer
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 55
Description
Although this approach works, it can be limiting. For example it prevents advanced configuration by extending directly from WebSocketMessageBrokerConfigurationSupport.
The preferred way to extend configuration is for Spring Session to provide a concrete WebSocketMessageBrokerConfigurer (similar to how Spring Boot customizes Spring MVC) probably along with an @EnableXxx annotation to import it.
From what I can see a specific challenge may be making sure an SessionRepositoryMessageInterceptor is registered for each endpoint. I think it should be possible to automate that in other ways.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining AbstractSessionWebSocketMessageBrokerConfigurer and WebSocketMessageBrokerConfigurationSupport, then trace how SessionRepositoryMessageInterceptor is registered for endpoints. Done means a concrete WebSocketMessageBrokerConfigurer and a proposed @EnableXxx integration provide the preferred extension path while ensuring the interceptor is registered for each endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100