Why is it that you need an HttpSession in order to get a ServletContext? I tried to obtain a ServletContext using an HttpServletRequest, but this isn't possible in the API, unless you do a request.getSession().getServletContext().
This creates a session, however, and I'm not sure I need a session to be created at the point in time where I am obtaining the ServletContext - all I want to do is have access to something I put in application scope earlier on. If I do a request.getSession(), then a session is started. If I do a request.getSession(false), then a NullPointerException will be thrown if I call getServletContext() on it. Why has the API been designed in such a way - after all, since it's possible to know what servlet context each request is going to, then shouldn't you be able to get the servlet context from the request? Thanks. -- View this message in context: http://www.nabble.com/HttpSession-questions-tf4008885.html#a11385003 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
