It is not easy to get to the ServletContext in a websocket session

[glassfishrobot]

You could use a Configurator for this:

public class GetServletContextConfigurator extends ServerEndpointConfig.Configurator
{
@OverRide
public void modifyHandshake(ServerEndpointConfig config,
HandshakeRequest request,
HandshakeResponse response)

{ EndpointConfig.getUserProperties().put("ServletContext",((HttpSession)request.getHttpSession()).getServletContext()); }

}

But that doesn't work for me, because there is no http session..
and the above call does not create it. It could be made that that always just creates a session, but can then a jsessionid cookie be send back over that upgraded websocket request so that the browser does use that?

I need the ServletContext to read files and that kind of stuff right from the WAR. Its impossible to get to that directory (or war file itself if it is not extracted) in side a websocket.

I think what we need is

EndpointConfig.getUserProperties().put("ServletContext",request.getServletContext());

or something like that.

Affected Versions

[1.0]

[glassfishrobot]

@glassfishrobot Commented
Reported by jcompagner

[glassfishrobot]

@glassfishrobot Commented
beamerblvd said:
I would suggest adding a getHttpContext (alternatively getApplicationContext) method to WebSocketContainer:

public interface WebSocketContainer
{
    ...
    /*
     * Returns the HTTP application context for the current deployed application. This can be anything,
     * but in a Servlet API environment it should be a {@code javax.servlet.ServletContext}.
     * 
     * @return the HTTP application context, such as the {@code ServletContext}, but never {@code null}.
     */
    Object getHttpContext();
    ...
}

If provided in this manner, getting a ServletContext is as simple as, using a Session as an example, this:

...
    @OnOpen
    public void sessionOpened(Session session)
    {
        ServletContext context = (ServletContext)session.getContainer().getHttpContext();
    }
    ...

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA WEBSOCKET_SPEC-217

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/websocket-spec/issues/217
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @pavelbucek

[markt-asf]

This is covered by #238