----- Original Message ----- From: "Morten Wilken" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 22, 2003 12:40 PM Subject: [OS-webwork] proposed small change to ww 1.3 > i would like to be able to change the httprequest in an action using the > ServletActionContext.setRequest() method.
Hi Morten, I do not think this should be added for the 1.3 release. We are fixing the last reported bugs now to be able to release it, and what you propose is more of a new feature which could have side-effects. I am not sure if I think it is a good idea to add it later on either. Would it mean that we say it is ok to change the request object anytime during the execution in your action? It could perhaps be hard to support that contract in all ww-code if people start using it? In your particular case, was it not possible to solve it using your own include tag instead? Best regards, Dick Zetterberg [EMAIL PROTECTED] > > when i use this method the most intuitive thing would be that the jsp's i > dispatch to will recieve my new Request object. > > today this isn't so. in the ServletDispatcher class the original request and > response object is used to forward to the jsp pages. > > what i would like was that lines similar to this: > > aRequest = ServletActionContext.getRequest(); > aResponse = ServletActionContext.getResponse(); > > were inserted into the ServletDispatcher class right after the Action has > been executed, and before dispatching to the jsp (ive put the at lines 191 > and 192). > ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
