Alex opened SPR-12172 and commented

I'm using a session bean with websocket scope and it works fine, but the bean is not available while handling the websocket application events like SessionConnectedEvent and SessionDisconnectEvent (if I try to access the bean I've an error telling me the scope is not available).

That is a problem because I'm unable to initialize the session bean during the connection phase, that could be very useful for my application.

I don't know if this can be fixed, if not a workaround will be very welcome :)

Affects: 4.1 GA

Referenced from: commits a99ef6d