Hello, I've got some pretty old code (which I may refactor at some point) which uses RequestContext.instance(javax.servlet.Servlet servlet, javax.servlet.http.HttpServletRequest request, javax.servlet.http.HttpServletResponse response)
I noticed this Important Note for the RequestContext.instance(javax.servlet.ServletContext servletContext, javax.servlet.http.HttpServletRequest request, javax.servlet.http.HttpServletResponse response) signature, but does this apply also to the above version, with javax.servlet.Servlet as first parameter?
I noticed this Important Note for the RequestContext.instance(javax.servlet.ServletContext servletContext, javax.servlet.http.HttpServletRequest request, javax.servlet.http.HttpServletResponse response) signature, but does this apply also to the above version, with javax.servlet.Servlet as first parameter?
public static RequestContext instance(javax.servlet.ServletContext servletContext, javax.servlet.ServletRequest request, javax.servlet.ServletResponse response) throws java.lang.ExceptionCreates a RequestContext from a ServletContext, ServletRequest and ServletResponse.
Important Note
Before we explain the benefits of creating your own RequestContext please take note that only one instance of this must be created and passed along during a requests life-cycle. In normal circumstances one will be created through the IDACall servlet and there will be no need for you to handle this explicitly.
Important Note
Before we explain the benefits of creating your own RequestContext please take note that only one instance of this must be created and passed along during a requests life-cycle. In normal circumstances one will be created through the IDACall servlet and there will be no need for you to handle this explicitly.
Comment