In WL6.1 request.getParameter returns NULL for URL parameters that exist

Question

          With the following URL, I get different results between WebLogic 4.5.1 and WebLogic
          6.1:
          http://phx-kmccarthy.medspecialists.net/tsweb/ParametersTest.jsp?apple=macintosh&tree&dog&country=USA
          Weblogic 6.1 returns:
          query string = apple=macintosh&tree&dog&country=USA
          apple = macintosh
          tree = null
          dog = null
          country = USA
          WebLogic 4.5.1 returns:
          query string = apple=macintosh&tree&dog&country=USA
          apple = macintosh
          tree =
          dog =
          country = USA
          here is the jsp...
          <%--
          * ParamtersTest.jsp which shows that empty parameters are ignored in WebLogic
          6.1
          --%>
          <%
          String apple, tree, dog, country;
          apple = request.getParameter("apple");
          tree = request.getParameter("tree");
          dog = request.getParameter("dog");
          country = request.getParameter("country");
          out.println("<br>query string = " + request.getQueryString());
          out.println("<br>apple = " + apple);
          out.println("<br>tree = " + tree);
          out.println("<br>dog = " + dog);
          out.println("<br>country = " + country);
          %>
          From the documentation on the getParameter() method:
          Returns the value of a request parameter as a String, or null if the parameter
          does not exist.
          In my opinion, not existing and being empty are different. Also, every other web
          application environment we've dealt with (including WebLogic 4.5.1) treats them
          as different. If the parameter doesn't have a value, (i.e. ...&tree&dog&...) then
          getParameter() returns the empty string, not null.
          As a result of this we have JSPs that break when running on 6.1.
          

Answer 1

Found the solution at last. Tomcat servlet container can't handle the chunked transfer-encoding that the J2ME Wireless Toolkit uses when you call outputstream.flush() in midlet. Using outputstream.close() instead of outputstream.flush() will avoid this problem for small requests. For all the codes in the articles on Http Post in Wireless Forum, don't use outputstream.flush() and it will run perfectly - Servlet's request.getParameter(parameterName) will work fine in doPost method.