To be precise - the method GET or POST is set in a header that is part of the original request - the servlet that the request is being forwarded to will examine the request and use the appropriate method. You can change the method by means of a custom request wrapper if necessary. Bill
To simplify what Bill said: if the original request was a GET request, a GET forward will be make; else if the original request was a POST request, a POST forward will be made. To circumvent this behavior, the professional method is to do as Bill said and create a wrapper request. The non-so professional method is to call either the doGet or doPost from each other and set some attributes as flags that will help you determine the proper course of action. I have use the latter approach for an application where a wrapper would not do.
SCJP, SCWCD, SCBCD, IBM CSD WebSphere v5, <br />A+, MCP 2000 and 2000 server, CST, and few incompleted certification tracks.<br /> <br />Ivory Coast<br /> <br />Analyze your web Request/Response @ <a href="http://webtools.servehttp.com" target="_blank" rel="nofollow">http://webtools.servehttp.com</a> down for a while...