Craig's correct. It's not legal in 3.x (and also won't work). However, if all you want to do is to set parameters, you can simply add them to the query string of the URL that you pass to getRequestDispatcher. ----- Original Message ----- From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, November 14, 2001 9:09 AM Subject: Re: Wrap an HttpServletRequest
On Wed, 14 Nov 2001, Diego del Río wrote: > Date: Wed, 14 Nov 2001 10:16:16 -0300 > From: Diego del Río <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Wrap an HttpServletRequest > > Is there any way to wrap an HttpServletRequest in Tomcat 3.2.x and then > forward the wrapped request to anoher servlet? > We need a 'decorated request' with added functionality, more precisely, we > need to add 'extra-parameters' to that request and then forward it to > another servlet that process both the original and the added parameters. In servlet 2.2 (Tomcat 3.x), it is not legal to wrap the request (or response) that you pass to a request dispatcher -- the only choice you have is to add request attributes. In servlet 2.3 (Tomcat 4.0), it is legal to wrap the request and response, as long as you subclass the provided wrapper base classes. You can do this for both request dispatchers and filters. > Thanks, > diego > Craig McClanahan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> *----* This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>