Github user isapir commented on the issue:
https://github.com/apache/tomcat/pull/76
@kkolinko I will create a ticket.
Unfortunately the issue with WebSocket is due to the JSR-356 specification.
I have spent a lot of time researching this issue and unfortunately that was
the only solution that I found.
It's weird and it's a hack, but unless the EG updates the spec that's all
we have.
See discussions at
https://stackoverflow.com/questions/21888425/accessing-servletcontext-and-httpsession-in-onmessage-of-a-jsr-356-serverendpo
https://stackoverflow.com/questions/17936440/accessing-httpsession-from-httpservletrequest-in-a-web-socket-serverendpoint
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
