views:

945

answers:

3

How can I access request headers from a SessionListener?

I need to set a timeout on the current session when it is created. The timeout needs to vary based on a header in the HttpServletRequest. I already have a SessionListener (implements HttpSessionListener) that logs the creation and destruction of new sessions, and it seems to be the most logical place to set the timeout.

I've tried the following, but it always sets ctx to null.

FacesContext ctx = FacesContext.getCurrentInstance();
A: 

You can't ( see the API ). The request allows you to access the session, but not the other way around.

You might even have concurrent requests for the same session, so this is not feasible.

Robert Munteanu
+6  A: 
erickson
+1  A: 
FacesContext ctx = FacesContext.getCurrentInstance();

JSF contexts are per-request and thread-local. So, this method call will probably return null outside the JSF controller invocations (e.g. FacesServlet.service) - so, other threads and any requests that don't pass through the Faces servlet mapping.

It is technically possible to set this time-out using a JSF mechanism - you could use a phase listener to check for a session after RENDER RESPONSE, though you would still have to cast to the servlet API to set the time-out. The advantage of phase listeners is that they can be registered either globally in faces-config (see spec) or for specific views. A global phase listener defined in a JAR with a META-INF/faces-config.xml can be dropped into multiple WARs, allowing you to easily reuse the functionality.

(You could also override how the session is provisioned to JSF, but the amount of work is excessive.)

For a one-off, erickson's suggestion of a Filter is really straightforward.

McDowell