spring-projects / spring-projects/spring-session
Question: Why HttpSesionListener are not called by the StandardSession?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 55
Description
Question:
Why the HttpSessionListeners registered in the web.xml are not called?
Why I should redeclare the HttpSessionListener as beans in the Spring context when they are already declared in the Servlet context?
It wouldn't be easier to delegate this calls to the StandardSession?
I found the spring-session integration is not transparent because of this.
Is there any reason why this API was designed liked this?
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 tracing how HttpSessionListeners declared in web.xml relate to Spring Session's StandardSession and Spring context integration. The issue provides no file or test entry point, so first identify the relevant servlet integration code and existing listener behavior. Done would require a decided API direction, such as documented rationale or transparent listener delegation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100