RequestDispatcherObject.include(req,res) causing problem in welogic 9.1

Question

I am migrating my application from web7.1. to 9.1.
In some servlets, i am using the RequestDispatcher.include method to paste a relevant JSP content.
When I access the servlets parameters values only after the requestDispatcherObject.include(req,res), the parameter values are returned as null.
For eg.
consider 2 parameter values , status,mode are present in a servlet, project.java.
I am including project.jsp file inside this servlet.
When I access the parameters only after the include statement, the values are returned as null, but when i access any one parameters before this statement, both the original parameter values are retained.
i.e.
/Project?status=disp&mode=true
Inside doGet method of Project .java:
String mode=HttpServletRequest.getParameter("mode");
RequestDispatcher reqdis=getServletConfig().getServletContext().getRequestDispatcher("/project.jsp");
reqdis.include(req,res);
String status=HttpServletRequest.getParameter("status");
System.out.println("status "+status+"\nmode "+mode);
The above code prints the value
status disp
mode true
However when we change the code as ,
RequestDispatcher reqdis=getServletConfig().getServletContext().getRequestDispatcher("/project.jsp");
reqdis.include(req,res);
String status=HttpServletRequest.getParameter("status");
String mode=HttpServletRequest.getParameter("mode");
System.out.println("status "+status+"\nmode "+mode);
the output is
prints the value
status null
mode null
Thsi problem occurs in weblogic 9.1, and is otherwise working fine in weblogic 7.
Do I have to make code change in all instances where this problem occurs , or is there any common solution.
Kindly help me solve this issue at the earliest

Answer 1

I tried reproducing this, and I don't observe the same behavior. I get the same values (those specified in the URL) regardless of whether I retrieve them before or after the include (or mixed as in your example).
          There is only one way I can think this might happen. If you are using HTTP POST and using getInputStream() or getReader() to read the body of the request, you could affect things. This is mentioned in the servlet spec. This would fit with your behavior. If your servlet reads a parameter, WLS will parse the all the parameters and they stay read-only (you can't set parameters, only attributes). WLS will only parse on demand for performance reasons (no point if one isn't requested). Nothing the included page can do will affect the parameters, so you'd see both be set. If the servlet includes the JSP first and the JSP calls getInputStream() and reads all the data, then when the servlet gets a parameter and WLS attempts to parse the POST body, there is no data left to be read (because the JSP already read it). Thus, everything will be null.
          But, in your example, it appears you are using GET. It shouldn't be possible if the parameters are set as part of the URL. And indeed, I don't see it.
          Perhaps your example is a simplification? What is your include doing?